Skip to content

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

Closed

Description

@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 OwnerCurrent Issue Owner: @strepanier03

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Dec 11, 2025
  2. melvin-bot commented on Dec 11, 2025

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

  3. melvin-bot commented on Dec 11, 2025

    @melvin-bot

    Triggered auto assignment to @arosiclair (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. melvin-bot commented on Dec 11, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. github-actions commented on Dec 11, 2025

    @github-actions
    Contributor

    👋 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.
  6. IuliiaHerets commented on Dec 11, 2025

    @IuliiaHerets

    Repro on Mac Chrome build 9.2.75-1. Duplicate feature still exists for splits despite

    Retest.3.1.mp4
  7. self-assigned this
    on Dec 11, 2025
  8. 9 remaining items

  9. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Dec 16, 2025
  10. 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
  11. melvin-bot commented on Dec 16, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  12. melvin-bot commented on Dec 16, 2025

    @melvin-bot

    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:

    • @jjcoffee requires payment through NewDot Manual Requests
  13. melvin-bot commented on Dec 16, 2025

    @melvin-bot
  14. strepanier03 commented on Dec 18, 2025

    @strepanier03
  15. strepanier03 commented on Dec 18, 2025

    @strepanier03
  16. jjcoffee commented on Dec 18, 2025

    @jjcoffee
    Contributor

    Thanks @strepanier03, but no payment is due here as it's a regression fix. Enjoy your time off!

  17. strepanier03 commented on Dec 18, 2025

    @strepanier03
    Contributor

    Oh great, thanks for the heads up @jjcoffee I'll remove that payment summary.

  18. JS00001 commented on Dec 19, 2025

    @JS00001
    Contributor

    Is this good to be closed?

  19. jjcoffee commented on Dec 22, 2025

    @jjcoffee
    Contributor

    @JS00001 Should be, QA will have verified it against the fix PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions