[Due for payment 2026-06-04] [Due for payment 2026-06-03] Workspace - Missing "your auto-categorization rules" when copying settings

[applause-bot]

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.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.

1. Go to staging.new.expensify.com
2. Go to Workspaces.
3. Click 3-dot menu on any workspace > Duplicate workspace.
4. Click Next.
   → Category row shows "x categories and your auto-categorization rules".
5. Close the RHP.
6. Click 3-dot menu on the same workspace > Copy settings.
7. 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.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7164100_1779869889104.6.mp4

View all open jobs on GitHub

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

Issue Owner

Current Issue Owner: @fedirjh

Issue Owner

Current Issue Owner: @fedirjh

[applause-bot]

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]

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

[melvin-bot]

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

[github-actions]

👋 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.

[MelvinBot]

Proposal

What is the root cause of that problem?

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.

[truph01]

Please assign me to this one

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

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.