[HOLD for payment 2024-10-14] [$250] [Search v1.2] Optimistically update search page when bulk holding/unholding expenses

[luacmartins]

Coming from here:

Just to note that a separate issue should be opened for the bulk action dropdown not updating, i.e. following these steps:

1. Select any unheld outstanding expense
2. Tap on the bulk action dropdown and select the option to Hold the expense
3. Open the bulk action dropdown again
4. Note that it still says Hold instead of Unhold

cc @jjcoffee @cretadn22

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021839331369548391692
• Upwork Job ID: 1839331369548391692
• Last Price Increase: 2024-09-26

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @trjExpensify

[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.

[cretadn22]

@jjcoffee For this bug, we're not resetting the selectedTransaction data in the search context when the new value is updated, resulting in outdated information.
My solution is to reset the selected transaction whenever the user clicks the hold/unhold option.

@jjcoffee @luacmartins

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021839331369548391692

[melvin-bot]

Current assignee @jjcoffee is eligible for the External assigner, not assigning anyone new.

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.45-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• Updated selected transaction If getting new updates #49829

If no regressions arise, payment will be issued on 2024-10-14. 🎊

For reference, here are some details about the assignees on this issue:

• @jjcoffee requires payment (Needs manual offer from BZ)
• @cretadn22 requires payment (Needs manual offer from BZ)

[melvin-bot]

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@jjcoffee] The PR that introduced the bug has been identified. Link to the PR:
• [@jjcoffee] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
• [@jjcoffee] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
• [@jjcoffee] Determine if we should create a regression test for this bug.
• [@jjcoffee] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
• [@trjExpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon: