-
Notifications
You must be signed in to change notification settings - Fork 50
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
Adding a group to a circle makes it "readonly" for the owner #973
Comments
I upgraded to NC 23 the instance on which I filed this issue.
So perhaps the root cause is that the UI is checking my belonging to the group and forgets to check that I'm also the owner of the circle. (Edited the issue description) |
Same issue here, with NC 22.2.5 WHEN User A is owner of the circle C |
I can confirm this issue on NC 23.0.3. Any workaround yet? UPDATE: This also affects the access rights to e.g. collectives (read only for the owner after adding a group which owner belongs to). |
It seems it only affect group, not sub-circles ? |
Just tested. The same behaiour holds if you add another circle instead of a group. |
Thanks for your further feedback @ArtificialOwl. I testeed more thoroughly and I wasn't aware of a subtle condition that is actually triggering it. If, using only the Contacts app, I create Circle 1, then Circle 2 (so I'm the owner of both) and then add Circle 2 to 1 or vice versa, it works. As a Collectives administrator user this behaviour is unwanted because it forces me to add people one by one to the circle instead of reusing my existing groups. |
#999 should fix this issue |
Version: 22.3 (just upgraded NC server from 22.2.5 to 22.2.6)
STEPS TO REPRO
EXPECTED BEHAVIOUR
The user can add/remove groups and members as usual
OBSERVED BEHAVIOUR
The UI changes as if the current user is not the owner of the circle anymore.
Until before upgrading NC server I was able to edit any circle I created.
The text was updated successfully, but these errors were encountered: