Tag - 'Error Importing Tags' when editing Budget

[izarutskaya]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 1.4.53-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/cases/view/2778053
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

Precondition: User is logged in OldDot and added Corporate Workspace. Custom Tag added.

1. Navigate to Corporate workspace settings > Tags.
2. Click on 'Edit Budget' for added tag.
3. Enable 'Edit Tag Budget'.
4. Set 'Total workspace budget', 'Per member budget' and 'Threshold Notification' > Save.
5. Go to main Reports tab > Add New Report.
6. Add Expense to report with a custom tag.
7. Submit report and Final Approve it.
8. Again, navigate to workspace setting > Tags.
9. Edit Total workspace budget' (or 'Per member budget').
10. Click 'Save'.

Expected Result:

The new value of Total workspace budget' (or 'Per member budget') saved.

Actual Result:

Popup with an error 'Error importing tags' appears. When user closes it, another popup 'Oops... an error has occurred!' appears. Old value is visible on the preview, but if user opens Edit Budget, new value is viewed.

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6416788_1710690076468.bandicam_2024-03-17_17-07-18-998.mp4

View all open jobs on GitHub

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

[mountiny]

This is oldDot blocker

[mountiny]

Closing in favour internal blocker https://github.com/Expensify/Expensify/issues/379920