-
-
Notifications
You must be signed in to change notification settings - Fork 815
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
Feature: An option for users to leave the Organization #1873
Comments
Will this require an corresponding issue in the API? |
@palisadoes There is no need for any API work for this. Already sufficient code is present in the API. |
do we have any existing UI for this @palisadoes |
We first need to get this left side of users completed in #1510 |
@pranshugupta54 that won't look good and it will be confusing for users
|
@pranshugupta54 leaving the organization shouldn't be this accessible. We need to implement a better design to prevent accidental actions. |
We should keep it easy to use, I know we want more user engagement but at the same time we want the platform to be easy to use. For accidentally leaving, we can implement two steps (using confirmation modal) |
Yeah, @pranshugupta54, if we're placing the 'leave organization' feature in the sidebar, a two-step process would definitely be more secure. |
I think keeping the "leave organization" feature in the sidebar won't be a good idea, as it may encourage users to leave the organization instead of increasing engagement.
|
As both @pranshugupta54 and @duplixx suggested we should keep it easily accessible with 2-step user flow. Screencast.from.05-04-24.11.20.59.PM.IST.webm |
We can use existing designs in Talawa, i think we have similar modal in Delete Org (For superAdmin). We can use that same design directly instead. |
@pranshugupta54 Yeah, we could surely do that to maintain design consistency throughout the project. |
@chandel-aman yup the conclusion is add 2-step modal for "leave organization" button |
I can take this up, I only have one assigned which is waiting for other issues to be resolved first. We'll need to wait for re-design to complete first |
This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue. |
So the final changes would be this?
|
|
@palisadoes This will solve both of our problems, the inconsistency of the design and the less user engagement. |
Any discussion on this issue, as this is still not implemented. I want to work on this once the design is decided. |
There should be the option to deselect the organization on the home screen where users select their organization. |
Or we can go with both, even that's okay I think. |
We can allow users to leave the organization both from the "All Orgs" view and from within a specific organization's view.
|
@palisadoes first of all thankyou to you that this repo is highly active as compare to other orgs , I have gone through the whole issue and would like to work on it , I wanted to implement this Enhancement and merge it , can you assign it to me |
Unassigning. Inactivity. No PR |
Can you please assign it to me @palisadoes |
i have solved the issue but confused how to create PR as i also have made some changes in the talawa-api repo |
Please refer to this guide: Also:
|
…alisadoesFoundation/talawa-admin#1873) (#2753) * Fixed: issue-#1873 * test file updated-1 * test file updated-1-a
…1873) (#2629) * Fixed: issue-#1873 * Fixed: issue-#1873 * Fixed: issue-#1873 * Fixed: issue-#1873 * Not title changed to title * Ensure case-insensitive email verification for leaving organization * Null check for organization data added * Refetching of orgs added after leaving org * GraphQL error scenarios to test cases Added * GraphQL error scenarios to test cases Added 1 * Downgrade vitest to 2.1.5 to resolve peer dependency conflict * fixed parsing error 1 * TSDoc comment added in LeaveOrganization.tsx 5 * LeaveOrganization.test.tsx file updated 1 * suggested changes are made * suggested changes are made 2 * optimizing testing file 1 * optimizing testing file 2 * optimizing testing file 2-a * Fixed: issue-#1873 * Fixed: issue-#1873 * Fixed: issue-#1873 * Fixed: issue-#1873 * Not title changed to title * Ensure case-insensitive email verification for leaving organization * Null check for organization data added * Refetching of orgs added after leaving org * GraphQL error scenarios to test cases Added * GraphQL error scenarios to test cases Added 1 * Downgrade vitest to 2.1.5 to resolve peer dependency conflict * fixed parsing error 1 * TSDoc comment added in LeaveOrganization.tsx 5 * LeaveOrganization.test.tsx file updated 1 * suggested changes are made * suggested changes are made 2 * optimizing testing file 1 * optimizing testing file 2 * optimizing testing file 2-a * suggested changes are made 3 * optimizing test file 3 * optimizing test file 3-a * optimizing test file 3-b * optimizing test file 3-c * optimizing test file 3-d * optimizing test file 3-e
Is your feature request related to a problem? Please describe.
There is no way for the user to exit/leave the Organization.
Describe the solution you'd like
An option on the left panel for users to leave the Organization.
Describe alternatives you've considered
Can discuss on design
Approach to be followed (optional)
A clear and concise description of approach to be followed.
Additional context
Add any other context or screenshots about the feature request here.
Potential internship candidates
Please read this if you are planning to apply for a Palisadoes Foundation internship PalisadoesFoundation/talawa#359
The text was updated successfully, but these errors were encountered: