-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD for payment 2024-12-07] [Search v1] Add bulk actions on Search #51911
Comments
Triggered auto assignment to @lschurr ( |
|
Triggered auto assignment to Design team member for new feature review - @dubielzyk-expensify ( |
Draft PR is ready, but we need to hold on the inline PRs. |
Any PR you want me to have a look at? |
@dubielzyk-expensify eventually this PR, but that's still on hold for other PRs |
Alright. Let me know and I'll give it a review when it's ready 👍 |
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. |
Relabelling as Lauren is OOO now. |
Triggered auto assignment to @VictoriaExpensify ( |
|
Current assignee @dubielzyk-expensify is eligible for the NewFeature assigner, not assigning anyone new. |
I know we're super close to being done here, but I'm popping it in #migrate anyway to track to completion, as making the action buttons available on the search page is central to support our plans to better support batch processing on the Search page. |
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. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.68-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-12-07. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
Removing you Vics :) |
Payment Summary
BugZero Checklist (@lschurr)
|
Payment summary is correct - please request in ND @Pujan92 :) |
$250 approved for @Pujan92 |
With this PR, we're introducing new inline actions on the Search page. The next step is to add bulk actions so users can batch process reports.
Issue Owner
Current Issue Owner: @lschurr / @VictoriaExpensifyThe text was updated successfully, but these errors were encountered: