Skip to content

[Due for payment 2026-11-11] Rules - Expense defaults rule that involve matching category is not duplicated #105859

Closed

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: 9.5.31-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: #104155
Email or phone of affected tester (no customers): nsjoijsdoisdjoi@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

  • Enable Rules.
  1. Go to staging.new.expensify.com
  2. Go to workspace settings > Rules.
  3. Click Add rule > Apply expense defaults.
  4. Create a rule that involves only matching category (leave matching merchant in the first section empty).
  5. Go back to workspace list.
  6. Click 3-dot menu on the workspace > Duplicate workspace > Next > Continue.
  7. Open duplicated workspace settings > Rules.
  8. Go to Expense defaults tab.

Expected Result:

Expense defaults rule that involve matching category will be duplicated.

Actual Result:

Expense defaults rule that involve matching category is not duplicated.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7304378_1793769315948.14.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7304378

Issue OwnerCurrent Issue Owner: @Krishna2323

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 4, 2026
  2. applause-bot commented on Nov 4, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/4747153243aa4cc1431ff301db5ffec1080a633294db1424ab9e35b6d63fb56f

  3. melvin-bot commented on Nov 4, 2026

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #104155

  4. melvin-bot commented on Nov 4, 2026

    @melvin-bot

    @luacmartins @JS00001 @situchan you have been assigned to this deploy blocker because you reviewed the offending PR: #104155

  5. melvin-bot commented on Nov 4, 2026

    @melvin-bot

    @Krishna2323 you have been assigned to this deploy blocker because you authored the offending PR: #104155

  6. melvin-bot commented on Nov 4, 2026

    @melvin-bot

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

  7. github-actions commented on Nov 4, 2026

    @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.
  8. JS00001 commented on Nov 4, 2026

    @JS00001
    Contributor

    This is a BE issue

  9. m-natarajan commented on Nov 4, 2026

    @m-natarajan

    v9.5.31-3, Windows 11 / Chrome and iPhone 15 iOS 26.6.1, not repro, Reverted

    05.11.2026_01.20.38_REC.mp4
    iOS.expense.defaults.mp4
  10. added and removed
    ReviewingHas a PR in review
    on Nov 4, 2026
  11. changed the title [-]Rules - Expense defaults rule that involve matching category is not duplicated[/-] [+][Due for payment 2026-11-11] Rules - Expense defaults rule that involve matching category is not duplicated[/+] on Nov 4, 2026
  12. melvin-bot commented on Nov 4, 2026

    @melvin-bot

    @Krishna2323 / @situchan

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.31-4 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 2026-11-11. 🎊

    The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ 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]. If no checklist is needed for this issue, you can click: [no checklist button]

  13. added
    ReviewingHas a PR in review
    and removed on Nov 5, 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.EngineeringReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions