Is there any way to delegate the version and components management to the Project Managers without delegating the full project admin permissions?
I want to let the PM create, merge, release ... their own versions and create and maintain the components, but avoiding the risk of changing the wf scheme, or the issue screen scheme by mistake.
In fact, this is a "decoupling" between the PM and Jira admin roles in our organization. Can you offer any thoughts about this?
Yes, that's exactly what Jira currently supports. Letting your PMs be Jira administrators is a recipe for complete disaster (except for me, because I've had a lot of work in the past undoing the mess it makes)
First, remove your PMs from System and Jira administration, then revise your permission schemes.
Specifically, "Administrate project" permissions allows a user to maintain versions, components, users and Greenhopper configuration in THAT project only.
Oooops, I think that I didn't explained that very well.
I don't want the PMs change the WF scheme applied to their own projects. (not changing the WF scheme itself!!).
The same applies for all other schemes (issues, screens, ...). The only operations I want to "delegate" are assigning people/groups to project roles, and managing versions and components.
Of course, PMs don't have Jira admin permissions :)
If you want to delegate create and manage versions for a project from administer project permission e.g. because you want to allow a certain user to create versions, but not to change project role memberships, then you can use Version Manager for JIRA plugin. This allows version management without need to give administer project permission to the user.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot