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

User list: No distinction between enabled and disabled users #4140

Closed
henning-gerhardt opened this issue Jan 8, 2021 · 4 comments · Fixed by #4289
Closed

User list: No distinction between enabled and disabled users #4140

henning-gerhardt opened this issue Jan 8, 2021 · 4 comments · Fixed by #4289

Comments

@henning-gerhardt
Copy link
Collaborator

In 2.x there was an distinction between enabled and disabled users which is missing in 3.x if you have a large user base:

  • disabled users was not displayed by default in the user list overview and you must switch them on to get displayed
  • disabled users was a little bit other displayed by an other text color (light gray instead of black for enabled users)
@matthias-ronge
Copy link
Collaborator

Maybe it would also make sense to sort deactivated users to the end (see also #4101, #4129, #3295).

@henning-gerhardt
Copy link
Collaborator Author

No, please do not sort them to end of list. Users should be sorted by their names independent of they are enabled or not.

@andre-hohmann
Copy link
Collaborator

I agree with @henning-gerhardt. A different sorting of names will be irritating.

@matthias-ronge
Copy link
Collaborator

I had only meant the initial sort, assuming that me is still able to manually switch to alphabetical by clicking the header. If you always have 450 deactivated users from 11 former clients between the 7 active users, that's annoying, too. And as far as I know we don't have a way to hide them at the moment. If you can hide / show them with a switch, they can also appear in alphabetical order, I agree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants