Repository navigation
[Due for payment 2025-06-02] [Due for payment 2025-05-30] Expense - Expense is duplicated in the expense report after moving expense to same report #62500
Description
Activity
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.Triggered auto assignment to @dangrous (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.💬 A slack conversation has been started in #expensify-open-source
👋 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:
- Identify the pull request that introduced this issue and revert it.
- Find someone who can quickly fix the issue.
- Fix the issue yourself.
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
6 remaining items
- changed the title
[-]Expense - Expense is duplicated in the expense report after moving expense to same report[/-][+][Due for payment 2025-05-30] Expense - Expense is duplicated in the expense report after moving expense to same report[/+]on May 23, 2025 Reviewinglabel has been removed, please complete the "BugZero Checklist".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:
If no regressions arise, payment will be issued on 2025-05-30. 🎊
@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]
- changed the title
[-][Due for payment 2025-05-30] Expense - Expense is duplicated in the expense report after moving expense to same report[/-][+][Due for payment 2025-06-02] [Due for payment 2025-05-30] Expense - Expense is duplicated in the expense report after moving expense to same report[/+]on May 26, 2025 The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.51-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-06-02. 🎊
@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]
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.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): dsjiojsdniosjod3@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.4 / Chrome
App Component: Search
Action Performed:
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:
Screenshots/Videos
Bug6838552_1747855040173.move.mp4
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @lschurr