The current "Administer Project" permission is WAY too inclusive.
Unfortunately not, once a user is granted with administer project permissions, he will be able to perform all admin functions of a projects.
There is no way we can isolate one from the other. Its either none or all capabilities that a user gains.
Rahul
This is really unfortunate. Rather than having to add everything myself I was hoping to grant the ability to manage components and versions to others, but also keep them out of other areas.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Rahul and Jobin answered this, but I'd like to add that Atlassian have said that they'd like to break up admin into more layers, and this sort of thing is one part of what they're looking at. As in https://jira.atlassian.com/browse/JRA-3156 (vote and watch...)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The roles edited by a project admin is applicable only for that project. They can't add/delete a role and the changes they make won't impact another project.
There is no way to limit it at the moment.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.