Rules - Category tax default is still applied after "Rules" are disabled.

[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.73-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: #99420
Email or phone of affected tester (no customers): ibellicotest+2766@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app) - Windows 11 / Chrome
App Component: Money Requests

Action Performed:

Prerequisite: Use an expensifail account.
Prerequisite 2: Account has a workspace with "Rules" and "Taxes" enabled.
Prerequisite 3: Have at least two non default taxes created.

1. Open the staging.new.expensify.com website.
2. Navigate to "Workspaces" > Workspace > "Rules"
3. Click on "Add Rule" > "Apply expense defaults" > "Category"
4. On "Category" field, select any category.
5. On "Tax" field, select any non default tax and save the rule.
6. Navigate to "More Features"
7. Disable "Rules".
8. Navigate to workspace chat.
9. Create a manual expense selelcting the category used for the created rule.
10. Open the just created expense.
11. Note that created rule is still applied, and "Tax" field was updated, despite "Rules" being disabled.

Expected Result:

Category tax default rule should no longer be applied after the "Rules" feature is disabled by the user.

Actual Result:

Category tax default rule is still applied on a newly created expense, despite the "Rules" feature being disabled.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7253508_1788791470186.Tax_Rule_6.mp4

View all open jobs on GitHub

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

[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/3302586966643275840cb10b8073abab2c45adf63afe35bbdac2c3b0b3f569c4

[melvin-bot]

@JS00001 recently merged #99420, but they are OOO right now, so I'll auto-assign someone else.

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

[melvin-bot]

Triggered auto assignment to @mjasikowski (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

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

[melvin-bot]

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