-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[$1000] FEATURE REQUEST: Allow navigating the list in the new group dialog with arrow keys #7648
Comments
Triggered auto assignment to @lschurr ( |
Triggered auto assignment to @roryabraham ( |
I have this working on a local branch but am currently scope-creeping and making arrow navigation work on all our OptionsLists, not just NewGroup. The one that's proving trickier is |
Just so you know I'm not just making stuff up, here's a draft PR with what I've got so far: #7702 🙃 |
Got my PR done and almost ready for review. It's a bit of a beast so I want to make sure I write up super thorough test / QA steps. |
@roryabraham Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@roryabraham Still overdue 6 days?! Let's take care of this! |
Okay, ended up being a very big PR but I think there's a lot of good changes there and it's very thoroughly tested. Excited to see how the review goes. |
Assigned to @rushatgabhane , he's reviewing and testing the PR, job price for doing so will be $500. |
PR is being reviewed, it's a bit large :) |
Yeah, I'll try to push it forward ASAP. I might split it into multiple PRs to make it easier for the reviewers too. @rushatgabhane would it be helpful it I split off the KeyboardShortcut library changes from the rest? |
@roryabraham participants being hidden is the main blocker for the PR. Splitting off KeyboardShortcut lib would be nice for the two tickets waiting on event bubbling to be implemented tho. (#7920 (comment), #7623) |
I'm sure we'll be able to fix the participants being hidden bug, but frankly this just isn't as high priority as some other issues I've got assigned to me at the moment. So I'm going to create a separate PR for the KeyboardShortcut lib upgrades then follow-up with this as soon as I can. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a production regression has occurred a Root Cause Analysis is required. Please follow the instructions here. 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. |
11 similar comments
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a production regression has occurred a Root Cause Analysis is required. Please follow the instructions here. 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 production regression has occurred a Root Cause Analysis is required. Please follow the instructions here. 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 production regression has occurred a Root Cause Analysis is required. Please follow the instructions here. 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 production regression has occurred a Root Cause Analysis is required. Please follow the instructions here. 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 production regression has occurred a Root Cause Analysis is required. Please follow the instructions here. 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 production regression has occurred a Root Cause Analysis is required. Please follow the instructions here. 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 production regression has occurred a Root Cause Analysis is required. Please follow the instructions here. 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 production regression has occurred a Root Cause Analysis is required. Please follow the instructions here. 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 production regression has occurred a Root Cause Analysis is required. Please follow the instructions here. 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 production regression has occurred a Root Cause Analysis is required. Please follow the instructions here. 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 production regression has occurred a Root Cause Analysis is required. Please follow the instructions here. 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. |
Oh no! I'm not sure what I did here or if this is bad - @roryabraham would you be able to lend some insight? |
Not sure why this auto-message is posting so many times, asking eng - https://expensify.slack.com/archives/C03TQ48KC/p1659380948350629 |
On it. |
Sorry about that everyone. We accidentally created a bug when adding the new reminder feature. I think it should be resolved now. Going to leave a quick test comment here to confirm that can be ignored. Test: #7648 |
📣 @parasharrajat You have been assigned to this job by @Christinadobrzyn! |
Please ignore the ping, Rajat, just adding some notes to this GH as the payment structure wasn't super clear.
Slack convo about this compensation here - https://expensify.slack.com/archives/C01SKUP7QR0/p1659537301960919 |
Umm.. I thought I was alreaady paid $500. I received $500 again 🤔 |
Yes, based on this comment, you should have been paid $1000 - I didn't see that at the time of paying you for this job so I added the additional $500 as a bonus. |
@Christinadobrzyn If I'm not mistaken, base comp is $1000. But there were regressions. So the total pay should be $500. |
Sounds good, I wasn't aware of the regressions, is it an option to reject the bonus? |
I'm not aware of any options to reject the bonus. But you can request a refund for it |
Sounds good, I just requested a refund @rushatgabhane @parasharrajat I also created this new job to pay you the $250 - https://www.upwork.com/ab/applicants/1554909413932630016/job-details Let me know when you've accepted the offer and I'll pay you. |
done! |
Paid @parasharrajat through this job posting - https://www.upwork.com/ab/applicants/1554909413932630016/job-details I think we're all set here! Let me know if there's anything else. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
User should be able to user arrow keys
Actual Result:
User is unable to use arrow keys
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platform:
Where is this issue occurring?
Version Number: 1.1.37-0

Reproducible in staging?: Y
Reproducible in production?: Y
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by: @puneetlath
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1644356006523069
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: