You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
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.
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.
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.
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.
@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.
CC: @Josh Berman
Here's a couple of related issues in the public issue tracker.
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.
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.
Hope this helps.
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!
Atlassian has provided a feedback for this issue... As a customer, I opened a official support request.
It seems Atlassian will not fix this SERIOUS issue.
If you have SEN number, open this issue in a formal way to Atlassian and argue this is not a "simple new feature". It's a REAL and CRITICAL Security breach. It's a DEFECT.
My workaround in consideration: I'll start to looking for an alternative to Atlassian solutions. The competitors certainly have solutions that implements the BASIC system administration rules and take care of a some-thousand-licenses' customer requests.
03/Jun/21 12:33 PM
Thanks for contacting Atlassian Support!
I'm XXXXX and I'll assist you in this case.
We believe you may be referring to the suggestion ticket below:
We have reached out to our project team again to get an update regarding the status of the feature request regarding the ticket above. Our product team has informed us that currently, there's no plan to implement the feature request in JRASERVER-12891.
This was not an easy decision and something that was decided after reviewing our current feature request backlog. We have a set of criteria that we use to decide which feature request that we would like to implement. In case you have missed it, you may take a look at the criteria in the link below:
Currently, we are focusing on delivering feature requests which bring benefits to a large number of users. We have been working hard to include more new features which are useful for our users and you may view the feature request that we have recently implemented from the Jira Release Notes below:
We understand that the user interest of feature request in JRASERVER-12891 is relatively high but there are other feature requests which bring benefits for a larger number of users that we are currently working on. We do realize that this feature is something that you would like to see in Jira and rest assured, we are not ruling out of implementing this particular feature request. It's just for now our plate if full with a feature request in our existing roadmap.
We would recommend you to watch the feature request ticket so you can be notified if there are any changes to the feature request. In case you have any additional feedback including how the JRASERVER-12891 will be beneficial for your users, feel free to add a comment in JRASERVER-12891 feature request ticket so our product team better understand users use case scenarios.
As for the workaround, there is a third-party plugin called Version Manager for Jira which might be useful for you. Perhaps you can test it out to see whether it suits your use case.
Please let us know in case of any questions regarding this scenario, then we will be happy to help you further.
[Remove the engineer name due to privacy aspects] | Atlassian Support Engineer
As a small vendor, I have decided to not go through the effort of Data Center certification by Atlassian. However, the Version Manager for Jira addon works perfectly fine with Jira Data Center, is fully supported from my side for Data Center and quite some customers are using it in Jira Data Center successfully. You can safely use it in Jira Data Center.
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.