nextcloud / nextcloud/user_saml
Groups after a migration that still have a local sibling cannot be distinguished on web UI
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 104
- Forks
- 85
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 16
Description
While they obviously have different group IDs the display name are equal and users may have a difficult time to tell apart which one to use, e.g. for sharing.
For example a local group with both ID and Displayname "Musicians" is found which cannot be migrated (users from mixed user backend), then a group with ID "SAML_Musicians" is created, because "Musicians" was reported as group upon a user's SAML login. The displayname for both groups will be the same though.
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
No files, tests, or entry points are named in the issue. Start by locating the web UI code that displays group names and IDs, then reproduce the local and migrated sibling groups; done means users can clearly distinguish the two groups when selecting one for sharing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100