Expense- Tag and category not shown after changing WS and going back in "To" field

[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: v9.2.2-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: Exploratory
Email or phone of affected tester (no customers): testpayment935+762aa@gmail.com
Issue reported by: Applause Internal Team
Device used: Windows 11 pro /Chrome, Samsung Galaxy s10/ Chrome
App Component: Money Requests

Action Performed:

Precondition - Have 2 WS with category and Tag

1. Navigate to staging.new.expensify.com
2. Go to FAB > Create expense
3. Enter amount and Next
4. Note there is Category and Tag to choose
5. Change "To" option to other WS
6. Change it back to WS 1

Expected Result:

There is option to choose category and Tag

Actual Result:

Tag and category not shown after changing WS and going back in "To" field

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

1.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @trjExpensify (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.

[trjExpensify]

Yeah, the coding fields available on the confirmation page should match those of the workspace selected. Any leads on the bug here? 🤔