Skip to content

[$250] Expense - Hold message is duplicated after splitting held expense #76005

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.63-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: Exp https://test-management.browserstack.com/projects/2219752/test-runs/TR-2155/folder/13176670/41237133/1035950351
Email or phone of affected tester (no customers): jdoijsdoijsnojosdi@gmail.com
Issue reported by: Applause Internal Team
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 > Hold.
  6. Enter reason and save it.
  7. Click More > Split.
  8. Click Save.
  9. Open any split.

Expected Result:

Hold message will not be duplicated after splitting held expense.

Actual Result:

Hold message is duplicated after splitting held expense.

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

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021994200224543854189
  • Upwork Job ID: 1994200224543854189
  • Last Price Increase: 2026-01-09
Issue OwnerCurrent Issue Owner: @RachCHopkins

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 25, 2025
  2. melvin-bot commented on Nov 25, 2025

    @melvin-bot

    Triggered auto assignment to @RachCHopkins (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. RachCHopkins commented on Nov 28, 2025

    @RachCHopkins
    Contributor

    So the Hold comment (the comment added as a reason when holding) is duplicated.

    After Hold:

    Image

    After Split:

    Image

    Also the expense history does not note the split. This seems like it's also an issue.

  4. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Nov 28, 2025
  5. changed the title [-]Expense - Hold message is duplicated after splitting held expense[/-] [+][$250] Expense - Hold message is duplicated after splitting held expense[/+] on Nov 28, 2025
  6. melvin-bot commented on Nov 28, 2025

    @melvin-bot
  7. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Nov 28, 2025
  8. melvin-bot commented on Nov 28, 2025

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane (External)

  9. marufsharifi commented on Nov 30, 2025

    @marufsharifi

    @sobitneupane, @RachCHopkins, is this still open for proposals?

  10. 32 remaining items

  11. mountiny commented on Jan 19, 2026

    @mountiny
    Contributor

    Given this has clear reproduction steps and does not make the user experience much worse, I am taking this our of quality. I will add the task to the canvas for backend engineers so they pick it up

  12. moved this to Bugs and Follow Up Issues in #expensify-bugson Jan 19, 2026
  13. c3024 commented on Jan 21, 2026

    @c3024
    Contributor

    This is not reproducible anymore for me.

    @jponikarchuk

    Could you please retest and confirm if this is still reproducible?

  14. self-assigned this
    on Jan 21, 2026
  15. jponikarchuk commented on Jan 21, 2026

    @jponikarchuk
    Author

    @c3024 This issue is not reproducible now

  16. mvtglobally commented on Jan 24, 2026

    @mvtglobally

    Issue not reproducible during KI retests. (First week)

  17. c3024 commented on Jan 26, 2026

    @c3024
    Contributor

    Not reproducible.

  18. moved this from Bugs and Follow Up Issues to Done in #expensify-bugson Jan 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.InternalRequires API changes or must be handled by Expensify staffWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions