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-06-04] [Due for payment 2026-06-03] Workspace - Missing "your auto-categorization rules" when copying settings #91805
Version Number: 9.3.83-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:#90220 Email or phone of affected tester (no customers):applausetester+ssndjois2jd@applause.expensifail.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:
Log in with Expensifail account.
Have at least two workspaces.
Go to staging.new.expensify.com
Go to Workspaces.
Click 3-dot menu on any workspace > Duplicate workspace.
Click Next.
→ Category row shows "x categories and your auto-categorization rules".
Close the RHP.
Click 3-dot menu on the same workspace > Copy settings.
Select any workspace > Next.
→ Category row shows only "x categories". "and your auto-categorization rules" is missing.
Expected Result:
On Copy settings page, Category row will show "x categories and your auto-categorization rules", similar to when duplicating workspace.
Actual Result:
On Copy settings page, Category row shows only "x categories".
"and your auto-categorization rules" is missing.
👋 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.
In CopyPolicySettingsSelectFeaturesPage.tsx:153, the categories case uses translate('workspace.common.categories') which resolves to just "Categories". The duplicate workspace flow at WorkspaceDuplicateSelectFeaturesForm.tsx:120 correctly uses translate('workspace.duplicateWorkspace.categories') which resolves to "categories and your auto-categorization rules".
What changes do you think we should make in order to solve the problem?
Change line 153 in CopyPolicySettingsSelectFeaturesPage.tsx to use translate('workspace.duplicateWorkspace.categories') instead of translate('workspace.common.categories'), matching the duplicate workspace flow. The same translation key change should be applied for es.ts and any other locale files.
Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.
changed the title [-]Workspace - Missing "your auto-categorization rules" when copying settings[/-][+][Due for payment 2026-06-03] Workspace - Missing "your auto-categorization rules" when copying settings[/+]on May 27, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.83-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@yuwenmemon@fedirjh 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]
changed the title [-][Due for payment 2026-06-03] Workspace - Missing "your auto-categorization rules" when copying settings[/-][+][Due for payment 2026-06-04] [Due for payment 2026-06-03] Workspace - Missing "your auto-categorization rules" when copying settings[/+]on May 28, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.88-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@yuwenmemon@fedirjh 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]
Activity
applause-bot commentedon May 27, 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/8f6952394c8156ff31b12544c197d7efeb41ec73783f878e81f3b5516a24a681
melvin-bot commentedon May 27, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #90220
melvin-bot commentedon May 27, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon May 27, 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:
MelvinBot commentedon May 27, 2026
Proposal
What is the root cause of that problem?
In
CopyPolicySettingsSelectFeaturesPage.tsx:153, the categories case usestranslate('workspace.common.categories')which resolves to just"Categories". The duplicate workspace flow atWorkspaceDuplicateSelectFeaturesForm.tsx:120correctly usestranslate('workspace.duplicateWorkspace.categories')which resolves to"categories and your auto-categorization rules".What changes do you think we should make in order to solve the problem?
Change line 153 in
CopyPolicySettingsSelectFeaturesPage.tsxto usetranslate('workspace.duplicateWorkspace.categories')instead oftranslate('workspace.common.categories'), matching the duplicate workspace flow. The same translation key change should be applied fores.tsand any other locale files.Next Steps for Contributor+ team: Reply with
@MelvinBot implement thisto create a draft PR,@MelvinBot <your feedback>to refine this analysis, or explain why you are rejecting Melvin's proposal.truph01 commentedon May 27, 2026
Please assign me to this one
melvin-bot commentedon May 27, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
1 remaining item
[-]Workspace - Missing "your auto-categorization rules" when copying settings[/-][+][Due for payment 2026-06-03] Workspace - Missing "your auto-categorization rules" when copying settings[/+]melvin-bot commentedon May 27, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.83-3 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-06-03. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon May 27, 2026
@yuwenmemon @fedirjh 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]
[-][Due for payment 2026-06-03] Workspace - Missing "your auto-categorization rules" when copying settings[/-][+][Due for payment 2026-06-04] [Due for payment 2026-06-03] Workspace - Missing "your auto-categorization rules" when copying settings[/+]melvin-bot commentedon May 28, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.88-2 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-06-04. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon May 28, 2026
@yuwenmemon @fedirjh 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]
fedirjh commentedon May 28, 2026
Should be fixed in #91241
melvin-bot commentedon Jun 1, 2026
@fedirjh Whoops! This issue is 2 days overdue. Let's get this updated quick!
melvin-bot commentedon Jun 3, 2026
@fedirjh Eep! 4 days overdue now. Issues have feelings too...
fedirjh commentedon Jun 5, 2026
This was fixed: