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 split is not marked as Split, but included as split in split details page #77326
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):hiuhuinuhihihihbuuih@gmail.com Issue reported by: Applause Internal Team Bug source: Pull Request QA execution Device used: Mac 26.1 / Chrome App Component: Money Requests
Action Performed:
Go to staging.new.expensify.com
Go to workspace chat.
Create an expense.
Open the expense report.
Click More > Split > Save.
Open any split.
Click More > Duplicate.
Open the duplicate expense and click Amount field.
→ Split label is not shown on Amount field. Amount field opens amount editor instead of split details page.
Open any split from Step 5.
Click Amount field.
→ Split details page actually includes the duplicated split from Step 8, but the duplicated split behaves like a standalone expense and not a split from Step 8.
Expected Result:
In Step 8 and Step 10, there should be a clear behavior whether the duplicated split should behave like a standalone expense or a duplicated split.
Actual Result:
In Step 8, Split label is not shown on Amount field. Amount field opens amount editor instead of split details page.
In Step 10, Split details page actually includes the duplicated split from Step 8, but the duplicated split behaves like a standalone expense and not a split from Step 8.
👋 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 [-]Expense - Duplicated split is not marked as Split, but included as split in split details page[/-][+][Due for payment 2025-12-23] Expense - Duplicated split is not marked as Split, but included as split in split details page[/+]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:
Activity
melvin-bot commentedon Dec 11, 2025
Triggered auto assignment to @strepanier03 (
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 @arosiclair (
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:
IuliiaHerets commentedon Dec 11, 2025
Repro on Mac Chrome build 9.2.75-1. Duplicate feature still exists for splits despite
Retest.3.1.mp4
9 remaining items
[-]Expense - Duplicated split is not marked as Split, but included as split in split details page[/-][+][Due for payment 2025-12-23] Expense - Duplicated split is not marked as Split, but included as split in split details page[/+]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
strepanier03 commentedon Dec 18, 2025
strepanier03 commentedon Dec 18, 2025
jjcoffee commentedon Dec 18, 2025
Thanks @strepanier03, but no payment is due here as it's a regression fix. Enjoy your time off!
strepanier03 commentedon Dec 18, 2025
Oh great, thanks for the heads up @jjcoffee I'll remove that payment summary.
JS00001 commentedon Dec 19, 2025
Is this good to be closed?
jjcoffee commentedon Dec 22, 2025
@JS00001 Should be, QA will have verified it against the fix PR.