I would like to be able to use a parent group for the purposes of granting atlassian application access.
When enabling nested groups on crowd and jira, and creating a group in crowd to grant application access to jira.
-user A is member of group B, member of group C
-group B is a member of group A
Jira cannot see the members of the nested group A, and when granting application access, group A shows 0 members.
Jira can see members of group C and thus sees user A, but requires adding more than one group to application access page than should be required.
Because as a user admin, it's not well managed to have members of jira-users and having to manually touch that group all the time, instead of that, use nested groups makes user management less of a chore to touch multiple groups, make changes to one group and it propagates upwards.
Nested groups is an On/Off configuration setting. Documentation at the link below, along with a few gotcha's for different environments and scenarios.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs