It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Jira - Permissions for Release

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.



4 answers

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.

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.

Like 1 person likes this

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

One more "yes, please!" here.

@Branden McElveenplease 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 

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.

1 vote

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.



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.



Like 1 person likes this

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

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Posted yesterday in Jira

Upcoming Enterprise releases targeting Q3 2019: Jira Software 8.5 & Jira Service Desk 4.5

Since launching the Jira Software 8.0 and Jira Service Desk 4.0 platform releases in February, many of you have been asking when the next Enterprise release will be so you can take advantage of the m...

218 views 1 4
Join discussion

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you