Skip to content

[Due for payment 2025-12-23] Expense - Duplicated expense auto-categorizes after removing category on the original expense #77320

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): isjdsoijsojnsiojisndj@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 with category.
  4. Open the expense and remove the category.
  5. Click More > Duplicate.

Expected Result:

The duplicated expense will not auto-categorize.

Actual Result:

The duplicated expense auto-categorizes.

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: @dylanexpensify

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 @dylanexpensify (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 @blimpich (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. dylanexpensify commented on Dec 11, 2025

    @dylanexpensify
    Contributor

    Confirming internally

  7. self-assigned this
    on Dec 11, 2025
  8. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Dec 11, 2025
  9. JS00001 commented on Dec 11, 2025

    @JS00001
    Contributor

    Demoting since we cpd a fix to disable this

  10. IuliiaHerets commented on Dec 11, 2025

    @IuliiaHerets

    Issue is no repro, no “Duplicate” option available anymore

    bandicam.2025-12-11.14-16-39-373.mp4
  11. removed their assignment
    on Dec 11, 2025
  12. jjcoffee commented on Dec 12, 2025

    @jjcoffee
    Contributor

    @dylanexpensify I think the issue needs to be kept open for now. We just temporarily disabled the duplicate option, but the issue potentially needs to be fixed.

    Having said that I'm not sure it definitely is an issue, because we're just calling requestMoney when duplicating, so it's the same as if you manually added a new expense with the same amount (it would also auto-categorize). I also don't know if we have any way to stop this happening. cc @JS00001 @garrettmknight

    (Confirmed that adding an expense with the same amount and merchant causes the same behaviour. It's a BE response so nothing we can do from the FE about it.)

  13. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Dec 16, 2025
  14. changed the title [-]Expense - Duplicated expense auto-categorizes after removing category on the original expense[/-] [+][Due for payment 2025-12-23] Expense - Duplicated expense auto-categorizes after removing category on the original expense[/+] on Dec 16, 2025
  15. 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
  16. melvin-bot commented on Dec 16, 2025

    @melvin-bot

    @jjcoffee @dylanexpensify 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]

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