[Bug]: For group admins: Groups in user list missing
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
A group admin can see all accounts that are in at least one of his administered groups under /settings/users.
In the list of accounts/users the column "Groups" ist empty. The group names appear after clicking the pen icon at the end of the line to edit one of the accounts.
Steps to reproduce
- Log in as an account that has group admin privileges to one or more groups but is not in the admin group (so doesn't have full user management privileges).
- Navigate to
/settings/users/ - See how the column "Groups" of the accounts list is empty
- See how the group namens in the column "Groups" appear after you clicked in the pen icon at then end of the line to edit one of the accounts.
- See how the column "Groups" is empty again after realoading the page.
| Before | After clicking "edit" |
|---|---|
Expected behavior
The column "Groups" should always show the groups that the rspective user is part of and the viewing user is a group admin of.
Nextcloud Server version
32.0.9
Operating system
None
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue at /settings/users/ with a group-admin account that is not in the admin group, comparing the initial list with the edit view. Trace how the user list obtains group names and verify that the Groups column shows the administered groups after reload, without requiring the edit action.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authorization, backend, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100