You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2025-12-23] Expense - Duplicated expense auto-categorizes after removing category on the original expense #77320
Version Number: 9.2.75-0 Reproducible in staging?: Yes Reproducible in production?: N/A - new feature, doesn't exist in prod If this was caught during regression testing, add the test name, ID and link from BrowserStack:#75323 Email or phone of affected tester (no customers):isjdsoijsojnsiojisndj@gmail.com Issue reported by: Applause Internal Team Bug source: Pull Request QA execution Device used: Mac 26.1 / Chrome App Component: Money Requests
👋 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.
@dylanexpensify I think the issue needs to be kept open for now. We just temporarily disabled the duplicate option, but the issue potentially needs to be fixed.
Having said that I'm not sure it definitely is an issue, because we're just calling requestMoney when duplicating, so it's the same as if you manually added a new expense with the same amount (it would also auto-categorize). I also don't know if we have any way to stop this happening. cc @JS00001@garrettmknight
(Confirmed that adding an expense with the same amount and merchant causes the same behaviour. It's a BE response so nothing we can do from the FE about it.)
changed the title [-]Expense - Duplicated expense auto-categorizes after removing category on the original expense[/-][+][Due for payment 2025-12-23] Expense - Duplicated expense auto-categorizes after removing category on the original expense[/+]on Dec 16, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.78-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@jjcoffee@dylanexpensify 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]
Activity
melvin-bot commentedon Dec 11, 2025
Triggered auto assignment to @dylanexpensify (
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 commentedon Dec 11, 2025
Triggered auto assignment to @blimpich (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Dec 11, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Dec 11, 2025
👋 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:
dylanexpensify commentedon Dec 11, 2025
Confirming internally
blimpich commentedon Dec 11, 2025
handling here: https://expensify.slack.com/archives/C01GTK53T8Q/p1765474725952029?thread_ts=1765465459.505229&cid=C01GTK53T8Q
JS00001 commentedon Dec 11, 2025
Demoting since we cpd a fix to disable this
IuliiaHerets commentedon Dec 11, 2025
Issue is no repro, no “Duplicate” option available anymore
bandicam.2025-12-11.14-16-39-373.mp4
jjcoffee commentedon Dec 12, 2025
@dylanexpensify I think the issue needs to be kept open for now. We just temporarily disabled the duplicate option, but the issue potentially needs to be fixed.
Having said that I'm not sure it definitely is an issue, because we're just calling
requestMoneywhen duplicating, so it's the same as if you manually added a new expense with the same amount (it would also auto-categorize). I also don't know if we have any way to stop this happening. cc @JS00001 @garrettmknight(Confirmed that adding an expense with the same amount and merchant causes the same behaviour. It's a BE response so nothing we can do from the FE about it.)
[-]Expense - Duplicated expense auto-categorizes after removing category on the original expense[/-][+][Due for payment 2025-12-23] Expense - Duplicated expense auto-categorizes after removing category on the original expense[/+]melvin-bot commentedon Dec 16, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.78-8 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-12-23. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Dec 16, 2025
@jjcoffee @dylanexpensify 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]