Skip to content
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

Add synchronization in deactivating users. #29891

Open
nimishmedatwal opened this issue Apr 30, 2024 · 2 comments · May be fixed by #29926
Open

Add synchronization in deactivating users. #29891

nimishmedatwal opened this issue Apr 30, 2024 · 2 comments · May be fixed by #29926

Comments

@nimishmedatwal
Copy link
Collaborator

Currently there is no synchronization between users table and deactivated users table ,when admin deactivates a user from Users table they have to reload the page for it to show in Deactivated users table. Similarly if they reactivate a user from Deactivated users table it is not shown in Users table without reloading the page.

Recording.2024-04-30.124245.mp4

CZO thread

@zulipbot
Copy link
Member

Hello @zulip/server-settings members, this issue was labeled with the "area: settings UI" label, so you may want to check it out!

@roanster007
Copy link
Collaborator

@zulipbot claim

roanster007 added a commit to roanster007/zulip that referenced this issue May 2, 2024
Previously, when a user is activated or deactivated through the
"Organization Settings", the corresponding tables of deactivated
or activated users are not updated until the modal is re rendered.

This is fixed by updating the table with new entries every time
a new event to either activate or deactivate the user is received.

Fixes zulip#29891
@roanster007 roanster007 linked a pull request May 2, 2024 that will close this issue
12 tasks
roanster007 added a commit to roanster007/zulip that referenced this issue May 2, 2024
Previously, when a user is activated or deactivated through the
"Organization Settings", the corresponding tables of deactivated
or activated users are not updated until the modal is re rendered.

This is fixed by updating the table with new entries every time
a new event to either activate or deactivate the user is received.

Fixes zulip#29891
roanster007 added a commit to roanster007/zulip that referenced this issue May 2, 2024
Previously, when a user is activated or deactivated through the
"Organization Settings", the corresponding tables of deactivated
or activated users are not updated until the modal is re rendered.

This is fixed by updating the table with new entries every time
a new event to either activate or deactivate the user is received.

Fixes zulip#29891
roanster007 added a commit to roanster007/zulip that referenced this issue May 2, 2024
Previously, when a user is activated or deactivated through the
"Organization Settings", the corresponding tables of deactivated
or activated users are not updated until the modal is re rendered.

This is fixed by updating the table with new entries every time
a new event to either activate or deactivate the user is received.

Fixes zulip#29891
roanster007 added a commit to roanster007/zulip that referenced this issue May 2, 2024
Previously, when a user is activated or deactivated through the
"Organization Settings", the corresponding tables of deactivated
or activated users are not updated until the modal is re rendered.

This is fixed by updating the table with new entries every time
a new event to either activate or deactivate the user is received.

Fixes zulip#29891
roanster007 added a commit to roanster007/zulip that referenced this issue May 2, 2024
Previously, when a user is activated or deactivated through the
"Organization Settings", the corresponding tables of deactivated
or activated users are not updated until the modal is re rendered.

This is fixed by updating the table with new entries every time
a new event to either activate or deactivate the user is received.

Fixes zulip#29891
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

4 participants