Expense - Report field is not removed when deleted

[kbecciv]

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.61-0
Reproducible in staging?: y
Reproducible in production?: n
Issue found when executing PR: #36039
Issue reported by: Applause - Internal Team

Action Performed:

Precondition:

• User is an employee of Collect workspace.
• The Collect workspace has some report fields.

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create a manual request.
4. Go to expense report.
5. Click on the report field > Add value > Save it.
6. On Old Dot, as admin, delete the report field in Step 5.
7. As employee, go to main chat and back to expense report (to receive update).
8. Click on the deleted report field.
9. Click 3-dot menu > Delete > Delete the field.

Expected Result:

The report field will be removed

Actual Result:

The report field is not removed. It is only removed after clearing cache and restart from Troubleshooting section.

Workaround:

n/a

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

Bug6443123_1712642141246.36039_desktop.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01dc85d44bb737c556
• Upwork Job ID: 1777733234423984128
• Last Price Increase: 2024-04-09

[melvin-bot]

Triggered auto assignment to @rlinoz (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ 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.

[kbecciv]

We think that this bug might be related to #wave-collect - Release 1

[mountiny]

cc @allroundexperts

[mountiny]

This is not a deploy blocker as report fields are not really used in NewDot by customers yet its a new feature for Newdot

@allroundexperts @thienlnam could you help with this one?