83857 migrate new task

[huult]

Explanation of Change

Fixed Issues

$ #83857
PROPOSAL:

Tests

Same QA step

• Verify that no errors appear in the JS console

Offline tests

QA Steps

1. Open the Expensify app.
2. Go to the workspace chat.
3. Tap + and select Assign Task.
4. Verify that the Assign Task page opens and you can navigate back normally.
5. Enter the required field (Title) and tap Continue.
6. Verify that the Assign Task Details page opens and you can navigate back normally.
7. Tap Title, Description, or Assignee.
8. Verify that each page opens and you can navigate back normally.

• 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 verified there are no new alerts related to the canBeMissing param for useOnyx
• 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: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

Screen.Recording.2026-07-02.at.11.45.16.mov

[melvin-bot]

@suneox 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]

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d1b362e7a5

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[codecov]

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines	Coverage Δ
src/ROUTES.ts	20.79% <ø> (+0.07%)	⬆️
src/SCREENS.ts	100.00% <ø> (ø)
src/libs/Navigation/linkingConfig/OldRoutes.ts	100.00% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts	76.92% <ø> (ø)
src/libs/actions/Task.ts	63.63% <0.00%> (ø)
.../pages/tasks/TaskShareDestinationSelectorModal.tsx	0.00% <0.00%> (ø)
src/pages/tasks/DynamicNewTaskDetailsPage.tsx	0.00% <0.00%> (ø)
src/pages/tasks/DynamicNewTaskDescriptionPage.tsx	0.00% <0.00%> (ø)
src/pages/tasks/DynamicNewTaskPage.tsx	0.00% <0.00%> (ø)
src/pages/tasks/DynamicNewTaskTitlePage.tsx	0.00% <0.00%> (ø)
... and 2 more
... and 15 files with indirect coverage changes

[suneox]

Manual test cases

DYNAMIC_ROUTES.NEW_TASK_DETAILS — Assign Task entry + back dismiss modal

---

Case 1.1 — Entry: report compose (+) → Assign task → opens task-details

Target: Task.ts:1083 (clearOutTaskInfoAndNavigate → createDynamicRoute). UI entry: AttachmentPickerWithMenuItems.tsx:359.

Precondition: logged in; workspace chat <R> open (user can comment). Clear stale task draft.

Onyx.merge('task', null);
// DERIVED: need a real report <R> with isAllowedToComment — open /r/<R> from LHN.

Steps:

1. Open the app → log in.
2. LHN → open a workspace chat (note <R>).
3. In compose, tap + → select Assign task.
4. Verify the Assign task details page opens (Title field + Continue/Next).
5. Verify URL contains suffix task-details on the report base, e.g. /r/<R>/task-details (not /new/task/details?backTo=).
6. Tap Back (header) → verify the task modal closes and you return to the report chat; URL no longer has task-details.
   Expected: Dynamic entry opens the correct page; new URL shape is correct; Back dismisses the modal to the report. No console errors.

---

Case 1.2 — Entry: Quick Action (FAB) → Assign task → task-details

Target: QuickActionNavigation.ts:65 → startOutCreateTaskQuickAction → Task.ts:1094.

Precondition: account with Assign task quick action configured.

Onyx.merge('task', null);
// DERIVED: quick action NVP + target personal details — needs a pre-configured test account.

Steps:

1. Open the app → log in.
2. Tap FAB (+) → select Assign task quick action.
3. Verify the Assign task details page opens.
4. Verify URL has suffix task-details on the current base path.
5. Tap Back → verify the modal dismisses correctly (no stuck stack).
   Expected: Quick action uses createDynamicRoute instead of ROUTES.NEW_TASK_DETAILS.getRoute(backTo); dismiss works.

---

Case 1.3 — Refresh / deeplink restore on new URL `…/task-details`

Precondition: on Assign task details (Case 1.1), URL e.g. https://dev.new.expensify.com:8082/r/<R>/task-details.

Steps:

1. Reload the page (Web) or reopen the app with the same URL (Mobile).
2. Verify the Assign task details page is restored (no 404, no home fallback).
3. Paste the URL into a new tab → Enter → verify it opens the details page directly.
4. Tap Back → verify return to report chat; suffix stripped.
   Expected: Refresh + deeplink of the new URL restore the correct stack.

---

Case 1.4 — ⚠️ Old URL /new/task/details?backTo=… (backward-compat P1)

Target: OldRoutes.ts — no entry for /new/task/* (see review P1).

Precondition: logged in; old URL https://dev.new.expensify.com:8082/new/task/details?backTo=%2Fr%2F<R>.

Steps:

1. Paste the old URL into the address bar → Enter.
2. Verify expected behavior after fix: redirects/opens equivalent /r/<R>/task-details.
3. ⚠️ Caveat (current PR): no OldRoutes / backTo-aware redirect yet — if details page does not open (fallback/home/404) = not PASS; capture as P1 evidence.
   Expected (after fix): old bookmark/deeplink resolves to the dynamic URL. Current PR: verify after author adds redirect or documents exception.

---

DYNAMIC_ROUTES.NEW_TASK — Confirm page (task-confirm) + back to details

---

Case 2.1 — Entry: details → Continue/Next → task-confirm

Target: DynamicNewTaskDetailsPage.tsx:106.

Precondition: on task-details (Case 1.1); Title entered.

Onyx.merge('task', {title: 'QC test task', shareDestination: '<R>'});

Steps:

1. Open Assign task details from workspace chat (Case 1.1).
2. Enter Title → tap Continue (or Next).
3. Verify the Confirm task page opens (Title / Description / Assignee / Share rows).
4. Verify URL has suffix task-confirm, e.g. /r/<R>/task-confirm.
5. Tap Back → verify return to details (/r/<R>/task-details), not straight to report.
   Expected: Forward details→confirm uses dynamic suffix; Back strips task-confirm to task-details.

---

Case 2.2 — Refresh / deeplink on URL `…/task-confirm`

Precondition: on confirm page (/r/<R>/task-confirm).

Steps:

1. Reload / paste deeplink → verify confirm page restores.
2. Tap Back → verify return to details (task-details suffix).
   Expected: Refresh/deeplink restore confirm page; back-nav correct.

---

Case 2.3 — ⚠️ Old URL /new/task?backTo=… (backward-compat P1)

Steps:

1. Paste https://dev.new.expensify.com:8082/new/task?backTo=%2Fr%2F<R> → Enter.
2. Verify after fix: equivalent to /r/<R>/task-confirm.
3. ⚠️ Current PR has no redirect — if confirm page does not open = not PASS.
   Expected: After OldRoutes/backTo-aware fix; currently depends on P1.

---

DYNAMIC_ROUTES.NEW_TASK_TITLE — Title sub-page from confirm

---

Case 3.1 — Entry: confirm → Title → back to confirm

Target: DynamicNewTaskPage.tsx:168 · DynamicNewTaskTitlePage.tsx:41.

Precondition: on confirm page (Case 2.1).

Steps:

1. From confirm page, tap Title row.
2. Verify Title edit page opens; URL suffix task-title.
3. Edit title → Save (or Back without saving).
4. Verify return to confirm (/r/<R>/task-confirm).
   Expected: Title sub-page open/back correct; useDynamicBackPath strips suffix to confirm.

---

Case 3.2 — ⚠️ Old URL /new/task/title?backTo=…

Steps: Paste old URL → verify after fix; ⚠️ current PR may fail (P1).

---

DYNAMIC_ROUTES.NEW_TASK_DESCRIPTION — Description sub-page from confirm

---

Case 4.1 — Entry: confirm → Description → back to confirm

Target: DynamicNewTaskPage.tsx:177 · DynamicNewTaskDescriptionPage.tsx:47.

Precondition: on confirm page (Case 2.1).

Steps:

1. Tap Description row on confirm page.
2. Verify Description page opens; URL suffix task-description.
3. Enter description → Save or Back.
4. Verify return to confirm (task-confirm).
   Expected: Description sub-flow back-nav correct.

---

Case 4.2 — ⚠️ Old URL /new/task/description?backTo=…

Steps: Paste old URL → verify after fix; ⚠️ current PR may fail (P1).

---

DYNAMIC_ROUTES.NEW_TASK_ASSIGNEE — Assignee selector from confirm (new-task flow)

---

Case 5.1 — Entry: confirm → Assignee → select user → back to confirm

Target: DynamicNewTaskPage.tsx:188 · DynamicTaskAssigneeSelectorModal.tsx:50.

Precondition: on confirm page; workspace has ≥2 members.

Steps:

1. Tap Assignee row on confirm page.
2. Verify assignee selector opens; URL suffix task-assignee.
3. Select a user → verify return to confirm with assignee updated.
4. Re-open Assignee → Back without selecting → verify return to confirm.
   Expected: New-task assignee flow uses DYNAMIC_ROUTES.NEW_TASK_ASSIGNEE; distinct from task-edit flow.

---

Case 5.2 — ⚠️ Old URL /new/task/assignee?backTo=…

Steps: Paste old URL → verify after fix; ⚠️ current PR may fail (P1).

---

[suneox]

Reviewer Checklist

• I have verified the author checklist is complete (all boxes are checked off).
• I verified the correct issue is linked in the ### Fixed Issues section above
• I verified testing steps are clear and they cover the changes made in this PR
  • I verified the steps for local testing are in the Tests section
  • I verified the steps for Staging and/or Production testing are in the QA steps section
  • I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
• I included screenshots or videos for tests on all platforms
• I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
• I verified tests pass on all platforms & I tested again on:
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
• I verified proper code patterns were followed (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 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)
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I verified that this PR follows the guidelines as stated in the Review Guidelines
• I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately and each prop has a /** comment above it */
  • The file is named correctly
  • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • The only data being stored in the state is data necessary for rendering and nothing else
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • All JSX used for rendering exists in the render method
  • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
• 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 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.
• For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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.
• I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

Manual test cases

---

DYNAMIC_ROUTES.NEW_TASK_DETAILS — Assign Task entry + back dismiss modal

---

Case 1.1 — Entry: report compose (+) → Assign task → opens task-details

Case 1.2 — Entry: Quick Action (FAB) → Assign task → task-details

Case 1.3 — Refresh / deeplink restore on new URL `…/task-details`

Case 1.4 — ⚠️ Old URL /new/task/details?backTo=… (backward-compat P1)

DYNAMIC_ROUTES.NEW_TASK — Confirm page (task-confirm) + back to details

---

Case 2.1 — Entry: details → Continue/Next → task-confirm

Case 2.2 — Refresh / deeplink on URL `…/task-confirm`

Case 2.3 — ⚠️ Old URL /new/task?backTo=… (backward-compat P1)

DYNAMIC_ROUTES.NEW_TASK_TITLE — Title sub-page from confirm

---

Case 3.1 — Entry: confirm → Title → back to confirm

Case 3.2 — ⚠️ Old URL /new/task/title?backTo=…

DYNAMIC_ROUTES.NEW_TASK_DESCRIPTION — Description sub-page from confirm

---

Case 4.1 — Entry: confirm → Description → back to confirm

Case 4.2 — ⚠️ Old URL /new/task/description?backTo=…

DYNAMIC_ROUTES.NEW_TASK_ASSIGNEE — Assignee selector from confirm (new-task flow)

---

Case 5.1 — Entry: confirm → Assignee → select user → back to confirm

Case 5.2 — ⚠️ Old URL /new/task/assignee?backTo=…

§6 — Cross-cutting (E2E · Share destination hybrid · Full back chain)

Case 6.1 — E2E: workspace chat Assign Task (matches PR QA)

Case 6.2 — ⚠️ Share destination (static NEW_TASK_SHARE_DESTINATION — P1 hybrid)

Case 6.3 — Full back chain: sub-page → confirm → details → dismiss report

[suneox]

@huult Test cases 1.4, 2.3, 3.2, 4.2, and 5.2 failed.

CleanShot.2026-07-07.at.20.20.21.1.mp4

[huult]

@suneox it's done

[suneox]

All test cases for the migrate task passed. Remaining migrate for next PR: Search and Bank

[huult]

@mjasikowski all yours

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[github-actions]

🚧 mjasikowski has triggered a test Expensify/App build. You can view the workflow run here.

[github-actions]

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #95112.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-0847e05cb13-aa76580-671fc1a80dee71e301dbf1f1b1c36f338be7ffd6/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-0847e05-aa76580-13162d9fcb35b0ead3337c4373f61c8541f819bf/index.html

Web 🕸️
https://95112.pr-testing.expensify.com

---

👀 View the workflow run that generated this build 👀

[OSBotify]

🚀 Deployed to staging by https://github.com/mjasikowski in version: 9.4.33-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	cancelled 🔪

[MelvinBot]

🤖 No help site changes required.

I reviewed the changes in this PR against the help site articles under docs/articles. This is a purely internal navigation refactor — it migrates the task-creation routes from the legacy backTo parameter to createDynamicRoute(), renames the screens/pages (e.g. NewTaskPage → DynamicNewTaskPage), and changes internal in-app URL paths (e.g. new/task/details → task-details).

None of this changes any user-facing behavior, flow, feature names, tab names, labels, or buttons. The "Assign a Task" flow (+ → Assign a Task → Title / Description / Assignee → Continue) works exactly as before.

The relevant help article — Assign a Task via Chat — is already accurate and requires no updates. The changed internal routes are not public help-site URLs, so no documentation links are affected either.

No draft docs PR was created.