Skip to content

BT - Migrate TASK_TITLE, REPORT_DESCRIPTION#86941

Open
mananjadhav wants to merge 4 commits intoExpensify:mainfrom
mananjadhav:mj-83371-bt-task-title-description
Open

BT - Migrate TASK_TITLE, REPORT_DESCRIPTION#86941
mananjadhav wants to merge 4 commits intoExpensify:mainfrom
mananjadhav:mj-83371-bt-task-title-description

Conversation

@mananjadhav
Copy link
Copy Markdown
Collaborator

Explanation of Change

Fixed Issues

$ #83371
PROPOSAL:

Tests

Task title (r/:reportID/title)

  1. Open the Expensify App and sign in.
  2. Open a chat that contains a task (or create a task in a report).
  3. Open the task so you see the task view (title, description, assignee).
  4. Tap Task title (or the title row) to edit the title.
  5. Observe the URL ending with /title after the report segment (e.g. r//title).
  6. Tap Back (or use the header back control).
  7. It should return to the report/task view (URL should not keep /title).
  8. Open the task title editor again, then refresh the page (browser reload).
  9. The title editor should load again and the URL should still end with /title.
  10. Tap Back again and confirm you return to the report/task view as in step 6.

Report / task description (r/:reportID/description)

  1. Open the Expensify App and sign in.
  2. Open a report or task where description is editable (room report or task).
  3. Open Description (task description row or room description from report details).
    Observe the URL ending with /description after the report segment (e.g. r//description).
  4. Tap Back. It should return to the previous report view (URL should not keep /description).
  5. Open the description editor again, then refresh the page.
  6. The description screen should load and the URL should still end with /description.
  7. Tap Back and confirm navigation matches step 5.
  • Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
android-bt-task-title-desc.mov
Android: mWeb Chrome
mweb-chrome-bt-task-title-desc.mov
iOS: Native
ios-bt-task-title-desc.mov
iOS: mWeb Safari
mweb-safari-bt-task-title-desc.mov
MacOS: Chrome / Safari
web-bt-task-title-desc.mov

@mananjadhav mananjadhav marked this pull request as ready for review April 2, 2026 07:35
@mananjadhav mananjadhav requested review from a team as code owners April 2, 2026 07:35
@melvin-bot melvin-bot bot requested review from huult and trjExpensify and removed request for a team April 2, 2026 07:35
@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Apr 2, 2026

@huult Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot melvin-bot bot removed the request for review from a team April 2, 2026 07:35
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 698c0258a7

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

}

Navigation.navigate(ROUTES.TASK_TITLE.getRoute(report?.reportID, Navigation.getReportRHPActiveRoute()));
Navigation.navigate(ROUTES.TASK_TITLE.getRoute(report?.reportID));
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve source route when opening task title editor

Navigating to ROUTES.TASK_TITLE.getRoute(report?.reportID) always builds r/:reportID/title, so the title page no longer knows whether it was opened from Search/Expense/other modal report contexts. Because TaskTitlePage now derives back navigation from the current URL, pressing Back from those contexts resolves to r/:reportID instead of returning to the originating route, which is a regression from the prior backTo behavior.

Useful? React with 👍 / 👎.

shouldCheckActionAllowedOnPress={false}
description={translate('reportDescriptionPage.roomDescription')}
onPress={() => Navigation.navigate(ROUTES.REPORT_DESCRIPTION.getRoute(report.reportID, Navigation.getActiveRoute()))}
onPress={() => Navigation.navigate(ROUTES.REPORT_DESCRIPTION.getRoute(report.reportID))}
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Open room description editor as a dynamic suffix route

This now navigates to the absolute path r/:reportID/description from Report Details, which drops the details context. RoomDescriptionPage computes its back target by stripping /description, so Back lands on r/:reportID instead of r/:reportID/details, pulling users out of the Details flow. Using a dynamic suffix route here is needed to preserve the correct return path.

Useful? React with 👍 / 👎.

@codecov
Copy link
Copy Markdown

codecov bot commented Apr 2, 2026

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/components/ReportActionItem/TaskView.tsx 0.00% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts 76.92% <ø> (ø)
src/pages/ReportDetailsPage.tsx 57.14% <0.00%> (ø)
src/pages/RoomDescriptionPage.tsx 0.00% <0.00%> (ø)
src/pages/tasks/TaskDescriptionPage.tsx 0.00% <0.00%> (ø)
src/pages/tasks/TaskTitlePage.tsx 0.00% <0.00%> (ø)
src/ROUTES.ts 15.70% <0.00%> (ø)
src/libs/TaskUtils.ts 20.68% <16.66%> (-0.15%) ⬇️
... and 12 files with indirect coverage changes

Copy link
Copy Markdown
Contributor

@trjExpensify trjExpensify left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

backTo project PR 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants