DEV: After deleting request money on Workspace, navigate to Concierge

[kavimuru]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Action Performed:

Pre-condition: Have a workspace

1. Click FAB => Request money
2. Input amount => Next
3. Select workspace = request
4. Click on request money message
5. Hover on cash message => delete
6. Observe navigate to the previous report and then navigate to Concierge

Expected Result:

Observe navigate to the previous report the same with request money for user

Actual Result:

navigate to the previous report and then navigate to Concierge

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

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

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: Dev
Reproducible in staging?: dev
Reproducible in production?: dev
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Screen.Recording.2023-08-03.at.09.16.19.mov

Expensify/Expensify Issue URL:
Issue reported by: @namhihi237
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1691028842094869

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[OSBotify]

👋 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 @PauloGasparSv (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[mvtglobally]

potentially related to #20908

[hayata-suenaga]

As @mvtglobally pointed out, this is an existing bug that is being fixed in #20908

Removing deploy blocker label and will keep track of this issue in the issue mentioned above

Also changing the priority to weekly

[hayata-suenaga]

actually changing the priority to monthly as the above issue where the cause is being fix has a monthly label (the fix needs a change in a library we rely on, and changing a library takes a time)

[sakluger]

Looks like the HOLD issue was fixed by another issue. @hayata-suenaga what does that mean for this issue?

[hayata-suenaga]

@sakluger thank you for letting me know about it

I tested the bug reproduction flow and confirmed that the issue was fixed by this PR.

@sakluger could you check if we need payment to the bug reporter and then close the issue 🙇

Screen.Recording.2023-09-05.at.1.07.56.PM.mov

[melvin-bot]

@sakluger, @hayata-suenaga Huh... This is 4 days overdue. Who can take care of this?

[melvin-bot]

@sakluger, @hayata-suenaga Huh... This is 4 days overdue. Who can take care of this?

[sakluger]

Thanks @hayata-suenaga!

All the issues linked to that PR were reported in June, and this issue was reported on Aug 2, so I don't think we need to pay for this bug report.