[Due for payment 2025-05-30] Expense - Expense is duplicated in the expense report after moving expense to same report

[nlemma]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.1.48-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to check - New feature
If this was caught during regression testing, add the test name, ID and link from TestRail: #62270
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Mac 15.4 / Chrome
App Component: Search

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Submit a manual expense.
4. Go to Reports.
5. Select the expense via checkbox.
6. Click dropdown button.
7. Click Move expense.
8. Click on the selected report.
9. Go back to workspace chat.
10. Click on the expense preview.

Expected Result:

The expense will not be duplicated in the expense report.

Actual Result:

The expense is duplicated in the expense report after moving expense to the same 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

Bug6838552_1747855040173.move.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @lschurr

[melvin-bot]

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

[nlemma]

@lschurr FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

[dangrous]

This is external, comes from https://github.com/Expensify/App/pull/62270/files#r2101102375 - trying a quick fix but commented to call it out to original authors

[dangrous]

PR up!

[techievivek]

Requested for a re-test here https://expensify.slack.com/archives/C9YU7BX5M/p1747911069659949

[IuliiaHerets]

@techievivek Tester can't reproduce the issue anymore

20250522_192506.mp4

[techievivek]

Thanks, gonna close this now.

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.50-0 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] Fix moving expenses from Search #62515

If no regressions arise, payment will be issued on 2025-05-30. 🎊

[melvin-bot]

@dangrous @lschurr @dangrous The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]