-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[Simple AA in NewDot] No option to leave workspace as non-owner #43508
Comments
Triggered auto assignment to @johncschuster ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.
What is the root cause of that problem?
What changes do you think we should make in order to solve the problem?
What alternative solutions did you explore? (Optional)
|
ProposalPlease re-state the problem that we are trying to solve in this issue.Admin is not able to remove himself from a workspace. What is the root cause of that problem?On the
What changes do you think we should make in order to solve the problem?As requested in this issue, we should not disable the "Remove from workspace" button for the user. We can remove the
We can modify the What alternative solutions did you explore? |
FYI we haven't added the |
Thanks for the update, @Beamanator. In that case, should this be |
@Beamanator, did the discussion land on this? |
Fair, maybe weekly is better 😅 I have been OOO yesterday and most of last friday so i have some stuff to catch up on, but the latest should be in the linked slack thread! I can try to look at this today soonish as well :D |
Discussion is still ongoing in Slack (looks like we're close to a path forward). Setting this to |
I think this fits under #wave-collect. @trjExpensify, would you agree? |
Did we conclude on this? #43508 (comment) Seems like it would be something we put in #wave-control and track with that to solve allowing anyone that's not the owner to freely leave a workspace. |
@johncschuster this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
I think we did! @Beamanator, as far as I can tell, this comment is the path forward, right? If so, can you give us a summary? |
Nice, ya i think so! So for the
Now the possibly interesting thing is: Once we implement this being possible, if a non-owner admin in a Control workspace see a warning about themselves being replaced with the Owner, in every member's policy chain? I kinda assume not, we'll just do that automatically? |
Given we've come to a conclusion, how about we switch this back to |
Thanks! I'm happy to stay on as the BZ 👍 Just wanted to get a sense check so I could apply the right level of urgency. I'll keep it bumping! |
Giving this a Melvbump since I'll be OOO tomorrow and Friday. Not overdue |
Happy Monday! I'm back with another Melvinbump. |
Bumping for Melv 👍 |
Bumping again to keep Melv at bay |
I'm OOO starting Monday, December 23, and will be returning Monday, January 6. I'll keep this bumping then! |
Hello everyone! I'm back from break! 👋 |
Okay, it looks like I'm the only assignee at the moment, and this issue is still low priority. I'm going to downgrade the label to We'll increase the priority again when the time is right 👍 |
Can we expand this to allow anyone to leave (except the owner), including both admins and members? More info here: |
Sounds good! I've updated the expected results in the OP as well as the repro/testing steps:
|
Ah! Jason made a great callout, here. I will need to update the OP to account for the following scenarios:
|
Yeah, and let's make sure we handle them appropriately. |
Hi! Wanted to sync up on this issue vs. this issue since it seems like they're basically the same. Should we consolidate? |
Yeah, I think consolidate makes sense. I wrote out some thoughts on the different cases and handling them a while back in this comment. |
It looks like we may not be consolidating these issues after all (per this comment in Slack) |
@MonilBhavsar do you have a moment to look at this? It looks like the functionality already exists (I saw you made the LeavePolicy command in Auth), just wasn't implemented fully in New Dot? Trying to sort out these long chains of comments. Thanks! EDIT: to be clear, I'm just trying to sort out what still needs to be done here. I think it's just showing/not showing the "leave" button in the appropriate situations, right? No backend work? |
That sounds right. We had an option to Leave policy in the three dot menu
Oh, I was looking as the policy owner. We still have the option to leave the workspace and it works fine |
Ah, FYI, I just commented on the app PR. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 1.4.81-8
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
Expensify/Expensify Issue URL:
Issue reported by: @Beamanator
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1718092341741619
Action Performed:
User A
, create policy in NewDotUser B
to workspace admin, and leaveUser C
as a regular userUser B
User C
Expected Result: Both
User B
andUser C
should be able to leave the workspaceExpected Result:
There should be a way for a workspace non-owner to leave a workspace.
Actual Result:
There's no way for either of the workspace non-owners to leave the workspace.
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Screen.Recording.2024-06-11.at.10.50.01.AM.mov
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: