Rules - Category tax default mentions 0% tax exempt rate when default rate is hidden in list

[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-3
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): applausetester+ssndjois2jd1@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.
• Enable Taxes and Rules.

1. Go to staging.new.expensify.com
2. Go to workspace settings > Categories..
3. Open any category.
4. Click Default tax rate.
5. Select 5% tax rate and save it.
6. Go offline.
7. Click Default tax rate.
8. Select 0% default rate and save it.
9. Go to workspace settings > Rules.
10. Go to Expense defaults.
11. Open the category tax default.
12. Click Tax field.

Expected Result:

In Step 10, category tax default will not mention 0% tax exempt rate because it is hidden in tax rate list in Step 12.

Actual Result:

In Step 10, category tax default mentions 0% tax exempt rate when it is hidden in tax rate list in Step 12.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7253708_1788803593093.13.mp4

View all open jobs on GitHub

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

[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/7b5312f2bd9db48940cff49ba945cb23a48c22df67f1c27c3321a89094485903

[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 @AndrewGable (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[MelvinBot]

⚠️ A setup step failed before I could start. This is usually a temporary issue — try again in a few minutes, and if it persists post in #melvinbot-ai.

Run details

[melvin-bot]

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