Getting administrator permissions for certain project (Jira software 9.4.21 Data Center Version)

Question

Some time ago I asked for administrator permissions for my project. I want to be able to change the workflow and other project parameters without having to create new project, delete exist project or add new users to my project.

I asked our support team about this but was refused. As far as I understand from the explanation of the guys, this is not a security issue. The version of Jira we use (Jira software 9.4.21 Data Center Version) cannot provide such capabilities. I'm not sure this is really true.

Can anyone help me clarify this issue.

Thank you.

ASM · Answer

Hello @Dave Mathijs Thank you for your answer.

I am not sure that I understand what wrong with my tags. Could you explain more?

I investigate you link and as I understand:

1. Jira administrator permissions allow me to change project workflows, right?

https://confluence.atlassian.com/adminjiraserver/working-with-workflows-938847362.html

2. The permissions provided does not depend on the Jira version, right?

Thank you.

ASM · Answer

First of all thank you for your answer.

I understand that there is a difference between a "project administrator" and a "Jira system administrator". I'm talking about project administrator permissions.

I conducted several experiments on the Jira that Atlassian provides for testing. I added few users with different permissions and users with administrator permissions are able to change project workflow and only for project where they administrator.

What are the reasons for the differences in behavior?

Does this somehow depend on the version of the Jira?

Thank you.

Nicolas Grossi · Answer

@ASM Welcome! Yes it is "in some way".

There is a project administration permission that cannot modify workflows, there is a system administrator permission that CAN modify workflows and many others things too (a potencial risk of bad usage) and there is like a root in linux that is belong to the administrator group.

Your support might have decided to not give you those groups/permission for "some" reason