-
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
[$250] WS switcher-Different back button behavior when creating workspace via + and Get started button #47603
Comments
We think that this bug might be related to #vip-vsb |
Triggered auto assignment to @JmillsExpensify ( |
@JmillsExpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
Edited by proposal-police: This proposal was edited at 2024-08-21 13:09:07 UTC. ProposalPlease re-state the problem that we are trying to solve in this issue.Different back button behavior when creating workspace via + and Get started button What is the root cause of that problem?
What changes do you think we should make in order to solve the problem?Following the same pattern used in WorkspaceCardCreateAWorkspace page, we shouldn't pass the active route ( App.createWorkspaceWithPolicyDraftAndNavigateToIt(); What alternative solutions did you explore? (Optional) |
Hmm interesting. I agree that's inconsistent. I think this comes down to whether we should move UP on pressing back or now. @marcaaron thoughts on this consideration? I can kind of see the argument that UP is a more valid action, so you should always be taken back to the workspace list. |
Not too passionate about this one as it's a pretty specific set of actions the user will take to uncover this inconsistency and can't imagine anyone feeling too impeded by either result. Both bring you to a list of workspaces. Both lead to the option to create a new workspace if you choose to do that after you just created one (which is probably an uncommon action in any case). Ignoring the rules of navigation for a second - I see the workspace selector as less of a "page" and almost more of a pop up selector menu from a UX POV so it doesn't really need to be something we can navigate back to. |
Cool, I agree with this. So then let's make sure that "back" goes to the workspace list for both of these cases. |
Job added to Upwork: https://www.upwork.com/jobs/~013645bc6cec0aa80d |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mananjadhav ( |
@JmillsExpensify, @mananjadhav Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@JmillsExpensify @mananjadhav this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@JmillsExpensify, @mananjadhav Still overdue 6 days?! Let's take care of this! |
Still waiting for proposals |
I have a proposal here #47603 (comment) |
@etCoderDysto Couldn't understand from your proposals if it covers the expected behavior ^ |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@JmillsExpensify, @mananjadhav Huh... This is 4 days overdue. Who can take care of this? |
Yes, the back button should navigate to the previous route. Sorry, missed this last week. |
@JmillsExpensify, @mananjadhav 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@JmillsExpensify, @mananjadhav 10 days overdue. I'm getting more depressed than Marvin. |
Not the highest priority, though I think we're still aligned that the back button is the previous route. |
@JmillsExpensify, @mananjadhav 12 days overdue. Walking. Toward. The. Light... |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
This issue has not been updated in over 14 days. @JmillsExpensify, @mananjadhav eroding to Weekly issue. |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
I'll review the proposals again on this one. |
A gentle reminder to look at this comment when reviewing proposals. Thanks! |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
1 similar comment
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Waiting on proposal review |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Missed this one. I'll check this by tomorrow. |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
1 similar comment
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: v9.0.21-4
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Action Performed:
Precondition:
Expected Result:
App will open workspace switcher when clicking app back button after creating workspace from Create a workspace" modal (should display the same behavior as when the + button is used).
Actual Result:
App returns to Account settings instead.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6574882_1723924338491.20240818_034344.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @mananjadhavThe text was updated successfully, but these errors were encountered: