Jira - Permissions for Release

[Kris]

We want to give access to our Developers so that they can create a Release version and Release. How can I do this in Jira. Could nit find a way to do so through Groups or other mechanisms.

[Brant Messenger]

I would like to request the "Release" functionality to be a separate item in the permission schema. I want to set a permission to a build group that is separate from the administrator of the project. This is an audit issue for us and should be treated as so. If my team needs to release I have to set them as administrators of the project, which is not a specific project role... it is a build role.

Hope this makes sense. I'm not sure how other teams handle this but this is an audit finding for my team.

[Eline Bijkerk]

Yes, please. This should not be connected to project admins - I don't necessarily want to give everyone project admin rights just so they can make releases.

[Carl-Marcus Scheffler]

Did you create a requirement with Atlassian for this? I would support it, if you did and share it with us...

[Nikhil Kundra]

Yes, please!

[Jon Karnofsky]

One more "yes, please!" here.

[Brant Messenger]

@somethingblueplease read the requests above.

WE (your customers) NEED a separate permission so that WE can assign a user that is NOT the project administrator the ability to action the "RELEASE" button and release the release.

Example of use would be a Development Manager or a DevOps lead, etc. It has been almost 2 years since you posted your response. Every other week people are up voting this request or adding the same request. Please slot for Jira's next release.

Thank you. 

CC: @Josh Berman 

[Greyson Yant]

Here's a couple of related issues in the public issue tracker.

• As a JIRA administrator, I want a specific set of permissions to see/manage project releases - JRACLOUD-67414
• Separate Project permissions for Version Management - JRACLOUD-34015
• New permissions item - version maintenance (v3) - JRASERVER-12891
• New permissions item - version maintenance (v3) - JRACLOUD-12891
• Security Violation: Manage Project Role Membership needs a Global Permission - JRASERVER-11884

Voting or commenting there may have better reach to the right eyes on Atlassian's teams. Those linked issues would also benefit from your concise user stories.

[Holger Schimanski]

I have created a Jira add-on Version Manager for Jira, which provides a new permission Manage Versions.

By assigning users or roles like Release Managers or Product Owners to this permission they can create and release versions without need for Administer Project permission.

See screenshots and description here.

Hope this helps.

Best regards,
Holger

[Matt Walker]

Holger Schimanski's solution only works for Jira Server, FYI. 

There does not appear to be any simple solution for this available to Cloud users.

[Chris_Green]

+1

[Marcus_Fuchs]

+1 for "Yes, please implement it."

[Ondřej Wretzl]

+1 please do IT

[marcosxsilva]

This is a kind of basic "business rule" of system administration... You must separate user management from any other system role! 

I don't want my configuration managers or project leaders with authority to add or remove users/permissions. Currently only Administrator role can add/edit Releases.

Also... More than 3 years and Atlassian has not provided a solution or alternative to this.

I'm very disappointed with Atlassian!

[Sam Heks-Tuit]

I think theres a very good case for this permission to be separated from the administer project permission. It's an audit and security issue. Not all those who work on releases need to administer the project.

[somethingblue]

Hi Kris,

Have you added the users as Project Admins? When you create a user that is not a project admin and go to the Kanban board that option is greyed out.  Per the Releasing a version knowledge base article you will need to have the JIRA 'Project Administrator' permission in the project(s) whose issues are to be included in the version.

As Jordan stated you can make changes to the permissiosn in the project under permisisons.

Cheers,

Branden

[Patrick Liétar]

In a board, when I have no filter enabled the release link is disabled and greyed out because it shows multiple projects of which I am not admin. When I filter on my project, it is enabled but gives the error below. And indeed, when I have my own board with only my project, I can use that link. Wouldn't that be a bug in JIRA? JSWSERVER-12930 could be related, appears as fixed on cloud but not on server.

[Jordan Berry]

This should be available through the permission scheme that is applied to your project

[Holger Schimanski]

To create a version and also to release it in Jira you need Administer Project permission. But this allows the respective users with this permission also to edit project role membership, which some companies like keep separate from creating and releaseng versions.

Therefor I have created a Jira add-on Version Manager for Jira, which provides a new permission Manage Versions. By assigning users or roles like Release Managers or Product Owners to this permission they can create and release versions without need for Administer Project permission.

See screenshots and description here.

For this version management an additional user interface is provided, because the standard user interface for version management is part of project config section only available for project admins.

Hope this helps.

Best regards,
Holger

P.S. I am not able to influence behaviour of Kanban or Scrum boards with my plugin. To release a version for a board, you still need Administer Project permission.  

[Olexiy C_]

Any chance to see it for Jira cloud? 

[pavuluriv]

Holger,

Is it possible to separate the create and edit version to Product Owners and Release version to Release Manager. It looks like all these are combined under Manage version permission from your screenshots

[noc_domrf_ru]

Да, пожалуйста.

[Melike]

I'm also following this issue.

[Marcello Lima]

I need too!

[Ashish Mehra]

Following!

[Alf H_ Solbjør]

Following!

[Florian FARIBAULT]

Following !