[$500] New order of tags do not update after reopening confirmation page

[m-natarajan]

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: 1.4.48-0
Reproducible in staging?: y
Reproducible in production?: New Feature
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:

Action Performed:

Precondition:

• User is an employee of Collect workspace.
• The Collect workspace has independent multilevel tags.

1. [Employee] Go to workspace chat.
2. {Employee] Go to FAB > Request money > Manual > Enter amount.
3. [Employee] On confirmation page, note the order of multilevel tags.
4. [Admin] On Old Dot, rearrange the order of multilevel tags (do not delete them)
5. [Employee] Without refreshing the page, repeat Step 2 and 3.

Expected Result:

The new order of multilevel tags will update when reopening the confirmation page, as it works (it updates) when changing tag name.

Actual Result:

The new order of multilevel tags does not update when reopening the confirmation page. It only updates after refreshing the page.

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

Add any screenshot/video evidence

Bug6404768_1709772124813.bandicam_2024-03-07_08-32-26-892.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0194dd2ee1e3003f2e
• Upwork Job ID: 1768169703946260480
• Last Price Increase: 2024-03-14

[melvin-bot]

Triggered auto assignment to @Christinadobrzyn (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

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

[m-natarajan]

@robertjchen FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

[m-natarajan]

We think that this bug might be related to #wave6-collect-submitters

cc@greg-schroeder