Is there any way a JIRA Admin can delegate some their high-level privileges to other users?

[Raj Vora]

Use case:

Since my team is new to JIRA, we are careful in limiting admin privileges to only a select few as to avoid catastrophe.  As you can image, our admin becomes inundated with a lot of "minor" admin-related tasks such as adding an option to a field that could potentially be done by someone else if they were granted the privileges.

Although I am aware someone can be delegated admin permissions to maintain a specific project (https://confluence.atlassian.com/adminjiraserver073/managing-project-permissions-861253293.html), is it possible to only delegate a specific subset of these privileges to specific individuals?  So for instance, in Project X, individual A is allowed to create a field and add, modify, remove options in those fields but not allowed to change the workflow for issue types.  This is just an example, obviously there are more permissions to consider.

[Raj Vora · Accepted solution]

Thanks.  So for someone who is a newbie to an admin role (in this case JIRA), what recommendations do you have to limit the possibility of irreversibly damaging the environment?  Are there some best practices documented online?  Obviously the only way you learn is to make mistakes, but you don't want to make big ones!

On that note, does JIRA log admin operations such as who created a field and when or who modified the workflow of a specific issue type?

[Kat Warner]

There is a lot of great advice and information here and in the associated book.

[Kat Warner · Accepted solution]

The early days are the best time to establish a group that considers and approves configuration requests.

'Minor tweaks' to fields can have a bigger impact in future especially is multiple fields are created by different teams with a very similar use. This limits reporting options and comparisons across projects.

[Alexey Matveev · Accepted solution]

Hello,

It is not possible in Jira Server. In Jira Cloud you can create a next-gen project. It is limited in features, but you do not have to be an Jira admin to create a field there or an issue type. Though select custom fields are not available there yet.