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

[Feature Request] Group Sorting #30946

Closed
TJHeeringa opened this issue Mar 28, 2018 · 10 comments
Closed

[Feature Request] Group Sorting #30946

TJHeeringa opened this issue Mar 28, 2018 · 10 comments

Comments

@TJHeeringa
Copy link

TJHeeringa commented Mar 28, 2018

Steps to reproduce

  1. Signin as Admin
  2. Press dropdown menu
  3. Open Users
  4. Observe the order of Groups

Expected behaviour

Groups are shown in alphabetical order.

Actual behaviour

Groups are shown order of creation.
Groups are shown in reverse-size order(sorted descending on number of members).

Server configuration

Operating system:
Ubuntu 16.04
Web server:
Nginx
Database:
MySql
PHP version:
7.1.2
ownCloud version: (see ownCloud admin page)
10.7
Updated from an older ownCloud or fresh install:
Updated
Where did you install ownCloud from:
ownCloud repo
Signing status (ownCloud 9.0 and above):
Admin

Client configuration

Browser:
Firefox Quantum
Operating system:
Windows 10

@ownclouders
Copy link
Contributor

GitMate.io thinks possibly related issues are #26890 (feature request: gpg key support), #12530 (Feature Request), #8569 (Feature requests), #2572 (Feature: Meta-Group "all"), and #6551 (Feature request: Support GPG/PGP (for E-Mail)).

@TJHeeringa
Copy link
Author

None of the above mention the issues truly. They are related, since they concern user sorting and one of them links to an issue that deals with sorting groups on the number of people.

This issue is concerned with that list of groups is not shown properly. See included screenshot.
capture

@phil-davis
Copy link
Contributor

phil-davis commented Mar 28, 2018

From what I can see, the ordering is working like:

  1. When the page first draws up:
  • Everyone
  • Admins
  • groups with members, most to least members (then alphabetical starting with uppercase, alphabetical starting with lowercase)
  • empty groups (alphabetical starting with uppercase, alphabetical starting with lowercase)
  1. When you create a new group on-the-fly then the list gets sorted:
  • Everyone
  • Admins
  • groups with members, most to least members (alphabetical not case-sensitive)
  • empty groups (alphabetical not case-sensitive)

The Groups dropdown for a user lists the groups like in (2) (with groups the user is a member of at the top)

So your example has groups in reverse order of size.

  • The difference between (1) and (2) - case-sensitivity of ordering - is a UI inconsistency that could be fixed.

@phil-davis
Copy link
Contributor

I guess this FR is thus asking for an option to sort groups alphabetically rather than in reverse size order.

@TJHeeringa
Copy link
Author

@phil-davis That is exactly the request.

@phil-davis
Copy link
Contributor

Note: in master the Users Page was recently moved to the https://github.com/owncloud/user_management repo. So if this FR happens, it needs to be done there, and if applied to the 10.0.* release series, then also done in core stable10

@TJHeeringa
Copy link
Author

@phil-davis Should I thus open the ticket at that repository?

@phil-davis
Copy link
Contributor

Yes please.

@DeepDiver1975 I suppose tickets should go in the newer app repos, as we split stuff out of core. And then after implementing some FR in the new repo, a decision can be made about if it is backported - and the backport might end up having to be done into core

@phil-davis
Copy link
Contributor

phil-davis commented Mar 28, 2018

See issue now raised in user_management repo:
owncloud-archive/user_management#14

@lock
Copy link

lock bot commented Jul 30, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants