It seems that a little while ago a similar question was asked and answered for the self-hosted version of Jira.
I'm myself one of a handful of full Jira Site-admins in our organisation. However, the permission management in each of our Jira projects has to be done by a much larger group of people, who have admin permissions in the respective Jira projects. That's the purpose of the project admin role and they know the best who should get which privileges in the Jira project.
Assigning project roles to user groups is preferred over assigning them for every single user, to for example cover entire developer teams or similar groupings, since that covers people joining or leaving such teams in the future.
To be able to determine whether a given permission/ project role is appropriate for a particular user group, it is essential that the Jira project admin can validate the current members of that group. It would also be helpful, if they could check the groups a given user is a member of, to try and generalise from an example case.
The only way those insights about group membership can be gained in Jira Cloud currently seems to be through Atlassian Administration, which means only by full Site-/ Org-admins. I couldn't find the parallel to what is described for the self-hosted solution in the linked question.
Have we missed anything? Are there workarounds out there, used by others? Why is this not available?
In our case this need gets amplified by the fact, that the company is growing quickly and changes to team (group) names and structures occur frequently, which means the project admins have to check and adjust the permissions to their projects accordingly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.