You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-11-11] Rules - Expense defaults rule that involve matching category is not duplicated #105859
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.
Go to staging.new.expensify.com
Go to workspace settings > Rules.
Click Add rule > Apply expense defaults.
Create a rule that involves only matching category (leave matching merchant in the first section empty).
Go back to workspace list.
Click 3-dot menu on the workspace > Duplicate workspace > Next > Continue.
Open duplicated workspace settings > Rules.
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.
👋 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:
Identify the pull request that introduced this issue and revert it.
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
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]
Activity
applause-bot commentedon Nov 4, 2026
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
melvin-bot commentedon Nov 4, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #104155
melvin-bot commentedon Nov 4, 2026
@luacmartins @JS00001 @situchan you have been assigned to this deploy blocker because you reviewed the offending PR: #104155
melvin-bot commentedon Nov 4, 2026
@Krishna2323 you have been assigned to this deploy blocker because you authored the offending PR: #104155
melvin-bot commentedon Nov 4, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Nov 4, 2026
👋 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:
JS00001 commentedon Nov 4, 2026
This is a BE issue
m-natarajan commentedon Nov 4, 2026
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
[-]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[/+]melvin-bot commentedon Nov 4, 2026
@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]