-
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-08-09] [$250] Remove checkboxes from table rows and implement selection mode on mobile devices #45451
Comments
Sure, I can take it! |
List looks good to me! |
Awesome, thanks Filip! |
I'll assign and be the BZ on this one. |
Current assignee @trjExpensify is eligible for the NewFeature assigner, not assigning anyone new. |
|
Triggered auto assignment to Design team member for new feature review - @shawnborton ( |
Job added to Upwork: https://www.upwork.com/jobs/~01832a2280e70e929a |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ikevin127 ( |
Added |
@shawnborton, @trjExpensify, @ikevin127, @filip-solecki Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Filip, you're still going to take this one right? |
Yes, I am going to work on this on Monday |
Not overdue, we're currently on track with starting work on this new feature as per the comment above. |
Great stuff, thanks Filip! |
Triggered auto assignment to @jasperhuangg, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
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. |
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. |
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.15-9 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-08-09. 🎊 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:
|
|
There is a bug. Please take a look - #46096 (comment). |
cc @trjExpensify For payment, in case this fell off your radar. Note: There were regressions with this one, so payment should be halved, @jasperhuangg to confirm! |
Payment Summary
BugZero Checklist (@trjExpensify)
|
Yep! Payment summary as follows:
Regression tests for the Search project will be handled centrally. Offer sent. |
@trjExpensify Offer accepted, thank you! |
Paid, closing! |
Now that we've successfully implemented selection mode for the Search page, we'd like to reuse this same UX for all table rows that can be found on mobile. In order to do this, we will want to remove the checkboxes from all mobile tables and implement the same long-press to enable selection mode.
Here's a running list of the tables we'd want to update on mobile:
Note that for #rooms, we first need to update the members list to look more like the table style found in Groups first, and then we should make this change. We can handle that separately.
cc @Expensify/design @trjExpensify - can you think of anymore places?
Also cc @filip-solecki in case you want to take this one as a follow up. Thanks!
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @trjExpensifyThe text was updated successfully, but these errors were encountered: