Repository navigation
Expense - Report field is not removed when deleted #39919
Description
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.
- Go to staging.new.expensify.com
- Go to workspace chat.
- Create a manual request.
- Go to expense report.
- Click on the report field > Add value > Save it.
- On Old Dot, as admin, delete the report field in Step 5.
- As employee, go to main chat and back to expense report (to receive update).
- Click on the deleted report field.
- 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
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~01dc85d44bb737c556
- Upwork Job ID: 1777733234423984128
- Last Price Increase: 2024-04-09
Activity
melvin-bot commentedon Apr 9, 2024
Triggered auto assignment to @rlinoz (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Apr 9, 2024
👋 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:
kbecciv commentedon Apr 9, 2024
We think that this bug might be related to #wave-collect - Release 1
mountiny commentedon Apr 9, 2024
cc @allroundexperts
mountiny commentedon Apr 9, 2024
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?
melvin-bot commentedon Apr 9, 2024
Job added to Upwork: https://www.upwork.com/jobs/~01dc85d44bb737c556
melvin-bot commentedon Apr 9, 2024
Triggered auto assignment to Contributor Plus for review of internal employee PR - @allroundexperts (
Internal)thienlnam commentedon Apr 9, 2024
I believe this has to do with the pusher updates from oldDot not getting prefixed with expensify_ . I can take this
melvin-bot commentedon Apr 12, 2024
@allroundexperts, @thienlnam Whoops! This issue is 2 days overdue. Let's get this updated quick!
thienlnam commentedon Apr 12, 2024
The fix PR should be live now - need to retest
melvin-bot commentedon Apr 15, 2024
@allroundexperts, @thienlnam Whoops! This issue is 2 days overdue. Let's get this updated quick!
melvin-bot commentedon Apr 16, 2024
@allroundexperts, @thienlnam Whoops! This issue is 2 days overdue. Let's get this updated quick!
melvin-bot commentedon Apr 18, 2024
@allroundexperts, @thienlnam Huh... This is 4 days overdue. Who can take care of this?