nextcloud / nextcloud/server

[Bug]: "Limit to groups" only finds former name when group was renamed

Open
#51,677 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage 30-feedback bug feature: apps management feature: users and groups hotspot: account name handling
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

⚠️ This issue respects the following points: ⚠️
Bug description

If a group is renamed, "Limit to groups" takes the old group name, which seems to me like an id. However, if a group is renamed, it cannot be found by the actual name, which seems to me like a label, but with it's old name (serving as id). The old name can be seen in the URL when selecting the group in the "Users" section. However, this is a bit confusing since the rest of the GUI follows the label name of the group and the old name of the group needs to be known to select it.

Steps to reproduce
  1. Create random group like "original_group"
  2. Rename group to other name like "changed_group"
  3. Go to Apps section and find an app that allows limiting to like "Polls"
  4. Check box next to "limit to groups" and try to search for "changed_group" in the text field.
  5. Then try to search for "original_group" - this will be found.
Expected behavior

If you search for the renamed group name to find that one.

Nextcloud Server version

30

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are identified in the issue. Reproduce the renamed-group search from the Apps section, then trace the “Limit to groups” entry point and compare how the displayed name and lookup value are supplied; done means searching for the new group name finds the renamed group.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, php
Domain
backend, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.