Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×I would like to be able to use a parent group for the purposes of granting atlassian application access.
Currently:
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.
Nested groups is an On/Off configuration setting. Documentation at the link below, along with a few gotcha's for different environments and scenarios.
https://confluence.atlassian.com/adminjiraserver/managing-nested-groups-938847047.html
Cheers
Hello James,
i want to ask you why you are going to manage the application access on a such complicated way?
Kind Regards
Semi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
Make sense?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.