[$250] Expense - Self DM opens instead of transaction thread after merging with unreported expenses

[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.3.25-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #79766
Email or phone of affected tester (no customers): jsodjsodnjoisjdosij@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Go to self DM.
3. Create two expenses.
4. Open any expense.
5. Click More > Merge.
6. Select expense from Step 3 > Continue.
7. Select all the details from the selected expense in Step 6 (all the second options) > Next.
8. Click Merge expenses.

Expected Result:

Transaction thread will open (similar to production).

Actual Result:

Self DM opens.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7086422_1771884484694.4.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @thesahindia

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022026068707359737023
• Upwork Job ID: 2026068707359737023
• Last Price Increase: 2026-02-23

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #79766

[melvin-bot]

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

[melvin-bot]

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

[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.