[Due for payment 2025-12-23] Expense - Duplicated split is not marked as Split, but included as split in split details page

[jponikarchuk]

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.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:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create an expense.
4. Open the expense report.
5. Click More > Split > Save.
6. Open any split.
7. Click More > Duplicate.
8. 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.
9. Open any split from Step 5.
10. 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.

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

1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @strepanier03

[melvin-bot]

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]

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