Expense - Original report link is not preserved after changing report for the second time

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

Action Performed:

1. Go to staging.expensify.com
2. Go to workspace chat.
3. Submit an expense to the workspace chat.
4. Create an empty report.
5. Click on the expense preview from Step 3.
6. Click Report field.
7. Select the empty report from Step 4.
8. In the new report, click Report field on the transaction thread.
9. Select the first report from Step 3.

Expected Result:

After changing report for the second time, the system message for the first expense moving should display the original report.

Actual Result:

After changing report for the second time, the system message for the first expense moving should display the newest report. So there are two system messages with the same report link.

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

Bug6875373_1751414816063.20250702_080408.mp4

View all open jobs on GitHub

[melvin-bot]

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

[techievivek]

@cretadn22 Can you take a look at this, it seems to be coming from your PR here #64088