[Due for payment 2026-08-21] [$250] Audit Reports navigation and prioritize navigating to report routes

[luacmartins]

Problem

When users interact with the Reports page, if they are then navigated to the inbox, then they get confused and disoriented.

Solution

1. Audit all interactions a user can take on the Reports page.
2. Create a list of navigation events that redirect the user out of the Reports page, e.g. some page in the Inbox
3. Fix those navigation events to prioritize navigating to their Reports counter part so users stay in the Reports page.

Issue Owner

Current Issue Owner: @sobitneupane

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022033935420524243072
• Upwork Job ID: 2033935420524243072
• Last Price Increase: 2026-04-07

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane (External)

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~022033935420524243072

[mkzie2]

🚨 Edited by proposal-police: This proposal was edited at 2026-03-27 07:47:54 UTC.

Proposal

Please re-state the problem that we are trying to solve in this issue.

When users interact with the Reports page (Search tab with any filter — Chats, Expenses, Reports), certain actions redirect them to the Inbox tab, causing confusion and disorientation

What is the root cause of that problem?

All five scenarios share the same root cause: navigation calls use ROUTES.REPORT_WITH_ID (or dismissModalWithReport which also resolves to ROUTES.REPORT_WITH_ID) without checking whether the user is currently in the Search/Reports tab.

ROUTES.REPORT_WITH_ID is rendered inside ReportsSplitNavigator (the Inbox tab), so any navigation to it while the user is on the Search fullscreen navigator automatically switches them to Inbox.

The helper isSearchTopmostFullScreenRoute exists precisely to detect this context, but it is not used in any of the affected code paths:

Scenario	File	Key lines	Route used
1. Leave group chat	Report/index.ts — navigateToMostRecentReport	4343–4365	REPORT_WITH_ID or Concierge
2. Open expense in chat	MoneyRequestAction.tsx	113–146	REPORT_WITH_ID (default)
3. Assign / create task	Task.ts — createTaskAndNavigate	347–357	dismissModalWithReport → REPORT_WITH_ID
4. Reply in thread	Report/index.ts — navigateToAndOpenChildReport	2139–2151	REPORT_WITH_ID
5. Open task preview	TaskPreview.tsx	138–141	REPORT_WITH_ID

dismissModalWithReport in Navigation.ts also has no Search awareness: it checks NAVIGATORS.REPORTS_SPLIT_NAVIGATOR only, so when Search is the topmost full-screen navigator it always falls through to navigate(ROUTES.REPORT_WITH_ID).

What changes do you think we should make in order to solve the problem?

The consistent fix across all scenarios is: wherever we navigate to ROUTES.REPORT_WITH_ID, check isSearchTopmostFullScreenRoute() first and use ROUTES.SEARCH_REPORT instead so the user stays in the Search/Reports context.

Fix 1 — navigateToAndOpenChildReport (Reply in thread)

// src/libs/actions/Report/index.ts
+import isSearchTopmostFullScreenRoute from '@libs/Navigation/helpers/isSearchTopmostFullScreenRoute';

 function navigateToAndOpenChildReport(...) {
     const report = childReport ?? createChildReport(...);
-    Navigation.navigate(ROUTES.REPORT_WITH_ID.getRoute(report.reportID, undefined, undefined, Navigation.getActiveRoute()));
+    if (isSearchTopmostFullScreenRoute()) {
+        Navigation.navigate(ROUTES.SEARCH_REPORT.getRoute({reportID: report.reportID, backTo: Navigation.getActiveRoute()}));
+    } else {
+        Navigation.navigate(ROUTES.REPORT_WITH_ID.getRoute(report.reportID, undefined, undefined, Navigation.getActiveRoute()));
+    }
 }

Fix 2 — navigateToMostRecentReport (Leave group chat)

// src/libs/actions/Report/index.ts
 function navigateToMostRecentReport(...) {
+    if (isSearchTopmostFullScreenRoute()) {
+        Navigation.goBack(ROUTES.SEARCH_ROOT.getRoute({query: buildCannedSearchQuery({type: CONST.SEARCH.DATA_TYPES.CHAT})}));
+        return;
+    }
     const lastAccessedReportID = findLastAccessedReport(...)?.reportID;
     if (lastAccessedReportID) {
         Navigation.goBack(ROUTES.REPORT_WITH_ID.getRoute(lastAccessedReportID));
     } else {
         navigateToConciergeChat(...);
     }
 }

Fix 3 — TaskPreview (Open assigned task)

// src/components/ReportActionItem/TaskPreview.tsx
+import isSearchTopmostFullScreenRoute from '@libs/Navigation/helpers/isSearchTopmostFullScreenRoute';

-onPress={() => Navigation.navigate(ROUTES.REPORT_WITH_ID.getRoute(taskReportID, undefined, undefined, Navigation.getActiveRoute()))}
+onPress={() => {
+    if (isSearchTopmostFullScreenRoute()) {
+        Navigation.navigate(ROUTES.SEARCH_REPORT.getRoute({reportID: taskReportID, backTo: Navigation.getActiveRoute()}));
+    } else {
+        Navigation.navigate(ROUTES.REPORT_WITH_ID.getRoute(taskReportID, undefined, undefined, Navigation.getActiveRoute()));
+    }
+}}

Fix 4 — MoneyRequestAction (Open expense in chat)

shouldOpenReportInRHP already controls whether ROUTES.SEARCH_REPORT is used. The fix is to ensure this prop is passed as true when the parent renders inside the Search context. This should be set at the ReportActionItem level by checking isSearchTopmostFullScreenRoute().

Fix 5 — Task.ts createTaskAndNavigate (Assign task)

// src/libs/actions/Task.ts
+import isSearchTopmostFullScreenRoute from '@libs/Navigation/helpers/isSearchTopmostFullScreenRoute';

     if (!isCreatedUsingMarkdown) {
         InteractionManager.runAfterInteractions(() => { clearOutTaskInfo(); });
-        Navigation.dismissModalWithReport({reportID: parentReportID});
+        if (isSearchTopmostFullScreenRoute()) {
+            Navigation.dismissModal();
+        } else {
+            Navigation.dismissModalWithReport({reportID: parentReportID});
+        }
     }

What alternative solutions did you explore? (Optional)

N/A

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[abelhailefen]

🚫 Duplicated proposal withdrawn by 🤖 ProposalPolice.

[github-actions]

⚠️ @abelhailefen Your proposal is a duplicate of an already existing proposal and has been automatically withdrawn to prevent spam. Please review the existing proposals before submitting a new one.

[api-claude-dev]

🚫 Duplicated proposal withdrawn by 🤖 ProposalPolice.

[github-actions]

⚠️ @api-claude-dev Your proposal is a duplicate of an already existing proposal and has been automatically withdrawn to prevent spam. Please review the existing proposals before submitting a new one.

[chengyixu]

🚫 Duplicated proposal withdrawn by 🤖 ProposalPolice.

[melvin-bot]

📣 @chengyixu! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

1. Make sure you've read and understood the contributing guidelines.
2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
   
   Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>