[JIRA] Split or partially grant "Administer Projects" permission

[Sameera Shaakunthala [inactive]]

As described here, the "Administer Projects" permission provides the ability to change the following areas.

1. Project role membership
2. Components
3. Versions
4. Some of the project details

We want to have two roles in place, "Senior Admin" and "Junior Admin", where Senior Admin should be able to perform all of the above actions but Junior Admin should only be able to perform the last three (disallow changing role membership).

If "Administer Projects" permission is granted for both roles, both will be able to perform all. Is there any workaround to achieve the described requirement?

[Nic Brough -Adaptavist- · Accepted solution]

You'll need to write something to do this - I've not yet seen any plugins that separate out the admin rights.

See also https://jira.atlassian.com/browse/JRA-3156 - watch and vote!

[Bob Romeijn]

Any update on this? It is realy stupid that you should give a PM or Scrum master (whatever role) Admin rights to create a project....

[Nic Brough -Adaptavist-]

No. You still need to be an admin in order to create a project (and in most places that's a good thing)

[Bob Romeijn]

most places? I have never been in a company in which a PM should be an admin to create a project, 9 out of 10 tools have the functionality to grant specific authorization to specific roles, that's normal behavior. it's my honest opinion that this is a real flaw of the tool.

[EddieW]

We have a similar need, especially considering greenhopper also uses that permission for starting sprints, which seems very PM specific.

SO i logged an enhancement request with Atlassian

JRA-33573

[Timothy]

No, there is no workaround for your requirement.

[Sameera Shaakunthala [inactive]]

Any plugins? Is there a possiblity to achive this with an in-house developed plugin?

[Timothy]

The only thought that I have is to use the <security-constraint> in the web.xml itself to restrict the URLs.