[Due for payment 2025-09-30] Reports - Navigation between reports is inconsistent when searched with group-by:from

[mitarachim]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.2.3-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from TestRail: #61371
Email or phone of affected tester (no customers): dsjionsjosdijdso@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Search

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create two expenses in the workspace chat.
4. Click Submit on the expense report.
5. Create another expense.
6. Go to Reports > Expenses.
7. Search with group-by:from.
8. Expand your user row..
9. Tap View button on one of the two expenses from Step 3.
10. Use navigation arrow on the RHP to navigate to the expense from Step 5.
11. Note that user can navigate from the first report to the second report via navigation arrows, but cannot navigate from the second report to the first report because the navigation arrows are missing on the second report.

Expected Result:

User should be able to navigate from the second report to the first report because they can navigate from the first report to second report.

Actual Result:

User can navigate from the first report to the second report via navigation arrows, but cannot navigate from the second report to the first report because the navigation arrows are missing on the second report.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6939082_1757388806788.Screen_Recording_2025-09-09_at_11.32.01.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @johncschuster (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Triggered auto assignment to @marcochavezf (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[nkdengineer]

@JS00001 Do you think we should prevent setActiveTransactionThreadIDs for the groupBy is not report?

App/src/components/SelectionList/Search/TransactionGroupListItem.tsx

Lines 156 to 165 in a24b0c0

	const openReportInRHP = (transactionItem: TransactionListItemType) => {
	const backTo = Navigation.getActiveRoute();
	const reportID = getReportIDForTransaction(transactionItem);
	const siblingTransactionThreadIDs = transactions.map(getReportIDForTransaction);
	// When opening the transaction thread in RHP we need to find every other ID for the rest of transactions
	// to display prev/next arrows in RHP for navigation
	setActiveTransactionThreadIDs(siblingTransactionThreadIDs).then(() => {
	// If we're trying to open a transaction without a transaction thread, let's create the thread and navigate the user