Changing the name of the jira-administrators group

[John.Cockerham]

I have an instance of Jira, installed on a Linux Server, that is used by our Developers and uses our Windows AD for user authentication.  I have just installed ServiceDesk on a Windows Server and want to use the same Windows AD for user authentication and to identify administrators and users of the ServiceDesk application.  The issue is that all the Atlassian products, Jira, Confluence, ServiceDesk, etc. seem to use the same group "jira-administrators" to identify administrators.  The people assigned as Jira administrators and ServiceDesk administrators are completely different.  How can I rename the group used to identify administrators for the ServiceDesk application from jira-administrators to something like servicedesk-administrators?   This value seems to be hard coded and I can't find a way to either change it or re-define it.

[Nic Brough -Adaptavist-]

It is defaulted, and used all over the place, but it is not hard-coded.

You can not rename the group.  But you can create a new group, grant it the admin and application access rights and then delete the jira-administrators group  It won't let you do that until there is at least one active user in a group that allows full admin via the new group(s), but you can completely remove the jira-administrators group with a bit of effort.

However, there are a couple of apps that don't like this.  I am not sure if they are on Cloud, and it has been a while since I ran into one, but still, it's worth bearing in mind if you do go for removing this group.

[Andrew Laden]

Keep in mind that ServiceDesk is just a addon to jira. So when you say you want there to be servicedesk-administrators separate from jira-administrators, at a GLOBAL level this doesnt make sense. There is no different. 

At a project level, you can just assign the roles to the correct group. for your non-service desk projects assign jira-administrators to the administrator role in the project, and for your service desk ones, assign servicedesk-administrators.

However if either of these also has the global "Jira Administrators" or "Jira System Administrators" permission, they will be able to access the project anyway.

What are you trying to limit by having different groups?