[Due for payment 2025-08-07] Header link takes 2 steps back to expense report when reply is created in transaction thread

[jponikarchuk]

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.1.68-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: #64158
Email or phone of affected tester (no customers): sjdosijnsodijsdo@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Submit two expenses to the workspace chat.
4. Open expense report.
5. Click on any expense row.
6. Send a message in the transaction thread.
7. Right click on the message > Reply in thread.
8. Send a reply in thread.
9. Click on the header subtitle.

Expected Result:

App will return to the transaction thread because the reply is created in the transaction thread.

Actual Result:

App returns to the expense report, which is two steps back from the thread when the reply is created in the transaction thread.

This issue also happens when opening system message in thread when there are two expenses in the 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

1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @Christinadobrzyn

[melvin-bot]

Triggered auto assignment to @Christinadobrzyn (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 @Gonals (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.

[BlameGPT]

Possible culprit PRs for this issue

• Fix - Thread on a message in IOU creates an extra level of thread #64158: This PR directly addresses navigation and threading behavior when replying in a thread on an IOU/expense message, matching the issue's flow of replying in transaction threads and clicking header links.
• Fix offline behavior when reporting transaction #64023: This PR involves offline behavior and navigation related to reporting transactions and expense reports, which may affect navigation flows after submitting or interacting with expenses in workspace chats.
• fix - Expense - Expense preview is blank briefly when deleted offline and returning online #64082: This PR involves expense preview and navigation behavior after deleting expenses and returning online, which relates to expense report and transaction thread flows in the issue reproduction steps.