nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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?

Accepted answers

Udo Brand

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

All comments

Udo Brand

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

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.

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

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!

Holger Schimanski_9q47k4

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.

Tanya Botta

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

Tanya Botta

You can use Jira Automation to copy between two projects. Extended the Project Admin rights on a project used just for versions and components and let Jira Automation copy those across to your target projects. Keep in mind this isn't a sync, but a copy.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration

permission

permission-scheme