Report - "Tax rate was modified" error when moving track expense to WS after adding tax.

[jponikarchuk]

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.2.20-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 TestRail: #71319
Email or phone of affected tester (no customers): ibellicotest+1863@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb / Hybrid app) - Windows 11 / Chrome
App Component: Money Requests

Action Performed:

1. Create a new account
2. Create a workspace
3. Go to the workspace, More Features, and enable Categories (If not enabled yet) and Taxes.
4. Go to selfDM and create a new expense
5. Click on the newly created expense
6. Note that the expense has Category, Tax Rate, Tax Amount, and Report fields
7. Tap on the "Tax" field and select any rate.
8. Tap on the report field and select "Create Report"
9. Note that once the expense was moved, a "Tax rate was modified" error message appears on "Tax" field.
10. Navigate to the workspace where the expense was moved and open the expense report.
11. Note that after a few seconds, error disappears.

Expected Result:

When adding a tax rate to a track expense, and moving it to a new report, no error message should be visible on the "Tax" field-

Actual Result:

When adding a tax rate to a track expense, and moving it to a new report, a "Tax Rate was modified" error message appears on "Tax" field.
When navigating to workspace chat and reopening report, error disappears after some seconds.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

11.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @JmillsExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

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

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

[koko57]

cc @cristipaval I guess it's another one from #71319

should it be a deploy blocker?

[parasharrajat]

We can tackle this as a follow-up. It is not blocking the user.