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 is not created after duplicating IOU expense #77303
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):siodjosijdsojsojsodj@gmail.com Issue reported by: Applause Internal Team Bug source: Regression TC Execution Device used: Mac 26.1 / Chrome App Component: Money Requests
Action Performed:
Precondition:
Account does not have self DM.
Account does not have workspace.
Go to staging.new.expensify.com
Open 1:1 DM.
Create an expense.
Open the expense report.
Click More > Duplicate.
Expected Result:
Duplicated expense will be created in self DM or 1:1 DM
Actual Result:
Duplicated expense is not created when duplicating IOU expense.
👋 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.
changed the title [-]77285 Expense - Duplicated expense is not created after duplicating IOU expense[/-][+] Expense - Duplicated expense is not created after duplicating IOU expense[/+]on Dec 10, 2025
changed the title [-] Expense - Duplicated expense is not created after duplicating IOU expense[/-][+][Due for payment 2025-12-23] Expense - Duplicated expense is not created after duplicating IOU 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@NicMendonca 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 10, 2025
Triggered auto assignment to @NicMendonca (
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 10, 2025
Triggered auto assignment to @Gonals (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Dec 10, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Dec 10, 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:
[-]77285 Expense - Duplicated expense is not created after duplicating IOU expense[/-][+] Expense - Duplicated expense is not created after duplicating IOU expense[/+]jjcoffee commentedon Dec 11, 2025
@lanitochka17 Do you have a self-DM on that account?
jjcoffee commentedon Dec 11, 2025
I wonder if we should create a self-DM if one doesn't already exist (and there's no default workspace). This seems to be what happens on OD.
26 remaining items
[-] Expense - Duplicated expense is not created after duplicating IOU expense[/-][+][Due for payment 2025-12-23] Expense - Duplicated expense is not created after duplicating IOU expense[/+]melvin-bot commentedon Dec 16, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".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 @NicMendonca 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]
melvin-bot commentedon Dec 23, 2025
Payment Summary
Upwork Job
BugZero Checklist (@NicMendonca)
mallenexpensify commentedon Dec 24, 2025
Doesn't look like @jjcoffee is due payment here, didn't see review of the linked PR
melvin-bot commentedon Dec 27, 2025
@NicMendonca Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
jjcoffee commentedon Dec 29, 2025
Yup, this was a regression, no payment needed!
JS00001 commentedon Dec 29, 2025
Going to close out since no payment needed