delegate version and component management without granting full admin project permissions

[Alex Perez]

Hello,

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?

[Udo Brand · Accepted solution]

hmm, I think you got something wrong. A project Admin can not change the workflow or issue screen scheme without being a jira administrator. Please see here for the managing project permissions

[Holger Schimanski]

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. 

Best regards
Holger

[Nikoletta]

What do you suggest for Cloud? 

[Rahul Gundecha]

I have same query. What is the solution for JIRA cloud?

[Nic Brough -Adaptavist-]

Migrate to server and get the version manager.

[Rahul Gundecha]

Thanks Nic. However we can't migrate from Cloud to server to get this feature

[Nic Brough -Adaptavist-]

You mean "won't", not "can't".  Doesn't matter though.  Migration to server is the only way you can get it.

[Rahul Gundecha]

Yes, it doesn't matter  :-) 
In my first query itself, I mentioned that I am looking for the solution for JIRA cloud.

[Nic Brough -Adaptavist-]

And I have given you it.  No point in repeating the question, you have the answer.

[Rahul Gundecha]

I am checking if there is any update after the question asked by Nikoletta Ersok  on Aug 21, 2017 

Only answer I understand now is - as of 21 March 2018, there is no support in Cloud which does the exact same thing which was asked at the start of this thread:

delegate version and component management without granting full admin project permissions

[Nic Brough -Adaptavist-]

That is what I said.  I also gave you the available fix for it.

[Nikoletta]

Hi @Rahul Gundecha

There is an open feature request to implement this for Cloud: 

https://jira.atlassian.com/browse/JRACLOUD-12891

[Rahul Gundecha]

Hi @Nikoletta

Thanks a lot for providing the right link. I just voted on that link

[Nic Brough -Adaptavist-]

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.

[Tanya Botta]

In addition, you can consider using the API to create Components and Versions.

[Alex Perez]

My fault,

as PM they can view the project configuration (WFS applied, ISS ..) but they can't change the WFS applied to their project.

you are right!

[Alex Perez]

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 :)

[Udo Brand]

As Nic stated the "Administrate project" permissions allows exactly that