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.

Sign up for GitHub

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

Jump to bottom

[QA] naming collisions with normal groups #533

Open

jnweiger opened this issue Aug 25, 2022 · 1 comment

Contributor

jnweiger commented Aug 25, 2022

Seen with customgroups-0.7.0-rc.1 and 0.6.2 (not a regression)

Admin uses '+ add group' on the user account bob to give him a group 'bob-group'.
Admin navigates to settings -> customgroups and clicks 'create Group' with the same name 'bob-group'. BAD
- Both groups are distinct objects, e.g. user bob is not member in the second group. OK

Expected behaviour:

Existing normal group names cannot be used as custom groups.
Existing custom groups cannot be used a normal groups.

jnweiger mentioned this issue

customgroups 0.7.0 #527

Closed

42 tasks

Contributor Author

jnweiger commented Feb 21, 2024

Still seen with 0.9.0-rc.1
One bob-g is a normal group, the other is a custom group:
User has no hint, which is which. BAD.

jnweiger mentioned this issue

customgroups 0.9.0 release #620

Closed

43 tasks

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