-
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 2023-12-15] [$500] Web - Search Term in WorkspaceMembersPage lost when clicking on Invite #22534
Comments
Triggered auto assignment to @stephanieelliott ( |
Triggered auto assignment to @sakluger ( |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to Design team member for new feature review - @shawnborton ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Search string is lost when clicking on Invite members from What is the root cause of that problem?We are not passing the search string to Invite page
The Invite route is not receiving search string from What changes do you think we should make in order to solve the problem?We should change this to
so that search string is captured in route
and we initialize
Similar changes can be made if we want to use the search string in invite page in What alternative solutions did you explore? (Optional) |
ProposalPlease re-state the problem that we are trying to solve in this issue.The search term is not passed onto the next screen when clicking Invite in WorkspaceMembersPage . What is the root cause of that problem?No mechanism is currently in place for communicating the search term to the next screen and using this as the default value of the search input. What changes do you think we should make in order to solve the problem?The search term can be stored in Onyx upon clicking the Invite button, after which it can be retrieved in What alternative solutions did you explore? (Optional)N/A |
Just want to comment that this is definitely not a bug, this would be a feature request. I do think it's a clever idea to maintain the search term between the manage members page and the invite page, but we should not be paying out a bounty for this one. |
Which one is preferred in Expensify design philosophy for these kind of features? Send as search params or saving to and retrieving from Onyx? |
That's a good question for our engineers, so maybe once we start taking proposals, we can sort that out. |
There are two proposals here already, one with search params and one with Onyx 😆 |
It was intentional to clear search in #15661. But now the behavior is reversed? |
Oh, if that's the case then we can just close this out and consider it not a bug/feature request. |
I think the behaviour mentioned in that issue is better. I always type in the text box of members page even for new members without much thought. Then click on invite to find the search term missing. I think others also do the same frequently. I think workspace members -> invite page is common and the search string should remain in invite page. The behaviour in that earlier issue appears correct for me. |
There's already precedence for storing form values (which this effectively is) in Onyx using the |
I'm going to close this one since it looks like we already decided to consistently clear the value. |
Dropping here for reference since I just posted in #expensify-open-source
Thanks @c3024 for sharing this link. Should we reopen this as a feature request instead of a bug? I have a feeling many/most people think similarly to my thoughts above. I can take a poll in #expensify-open-source if it's be helpful. |
This could use a redesign, as |
I think we can demote this to weekly and wait for @DylanDylann updates. |
@DylanDylann , it's been 5 days since you were assigned, when can we expect a PR? |
@mallenexpensify I am working on it. Will open the PR today |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.9-5 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 2023-12-15. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
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:
|
Regression Test Proposal
|
Reporter: @c3024 paid $250 via Upwork (bug was reported in July) @c3024 , can you please accept the job and reply here once you have? Regression test GH |
Accepted. Thanks. @mallenexpensify |
Should be all set! @c3024 paid and comment above has been updated to reflect payment |
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:
Expected Result:
The TextInput now in InviteUser page should have the string searched in WorkspaceMembersPage because once no results are found for a search string in WorkspaceMembersPage the search string should be there in Invite Page so that it should not be typed again from beginning.
Actual Result:
Search string in TextInput of InvitePage is empty
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.38-3
Reproducible in staging?: y
Reproducible in production?: y
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-07-09.at.3.07.10.PM.1.mov
Recording.3520.mp4
Expensify/Expensify Issue URL:
Issue reported by: @c3024
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1688895491063239
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: