What is the difference between JIRA Administrator and JIRA System Administrator?

[Richard Cross]

The documentation is rather vague on this:

• JIRA System Administrators: Permission to perform all JIRA administration functions.
• JIRA Administrators: Permission to perform most JIRA administration functions. 

could someone provide a more specific answer?

[Nic Brough _Adaptavist_ · Accepted solution]

This is where the new documentation for version 7 seems to be letting Atlassian down, in my opinion.

See the rather better doc at https://confluence.atlassian.com/jira064/managing-global-permissions-720412521.html#ManagingGlobalPermissions-sysadmin

For version 7, you'd want to add something about the admin access to "applications" (i.e. Service Desk and Software) which is similar to "add ons", but other than that, the 6.4 docs cover the difference properly.

[Christoph]

For what it's worth: Here's the link for the 7.2 documentation on this issue:

https://confluence.atlassian.com/adminjiraserver072/managing-global-permissions-828787760.html

[Allie Ruby]

I'm still not understanding. The documentation says there is an exclusion list...but what CAN a JIRA Administrator do?

I'm specifically looking for:

• create spaces
• create JSD
• Create groups
• Create custom fields

[Nic Brough _Adaptavist_]

They can't create spaces, that's the job of a Confluence administrator.

They can create Service Desk projects, groups and custom fields.

Basically, they can do everything the system admins can except the exclusions - the list of "can do" is far longer than "can't"

[Allie Ruby]

Thank you so much for this prompt reply! Exactly what I was looking for :)

[Tim H_]

This page is helpful for understanding the answer to this question in JIRA Cloud.