Rules - Categories can be enabled from Rules when accounting is connected

[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.4.50-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: #95444
Email or phone of affected tester (no customers): applausetester+khcategory19@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.
• Disable Categories, then connect workspace to Sage Intacct.
• Enable Rules.

1. Go to staging.new.expensify.com
2. Go to workspace settings > More features.
3. Click Categories.
   → "Not so fast" modal opens.
4. Go to Go to workspace settings > Rules.
5. Go to Field requirements.
6. Click Create field requirement rule.
7. Click Category.
8. Click Enable Categories.

Expected Result:

Categories cannot be enabled when accounting is connected.

Actual Result:

Categories can be enabled from Rules when accounting is connected.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7225977_1785881698449.4.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7225977

[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/906f8e8aeb69006da5a9ccb264e3956f1861657df037b57a9c26354d23df4afb

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

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

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