-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
None
-
82
-
1
-
We would like the ability to control who has access to create/edit versions within a project. It appears the only way to currently do this is to grant the user project administrator permissions.
A way to control this in the permission schemes would work well.
- duplicates
-
- Gathering Interest
- is cloned from
-
- Under Consideration
- is duplicated by
-
- Gathering Interest
-
- Gathering Interest
[JSWSERVER-19959] Add granular permissions relating to version control
The entire "Administer Project" permission needs to be broken up into "Administer Users and Roles", "Manage Releases", and "Administer Project" (for changing name, description, etc of project). These are completely unrelated permissions in many environments and shouldn't be granted in a single bundle.
This would be very useful, please consider adding this into the permissions schema, why should "Create Versions" be different from other permissions, it doesn't make sense.
The original request (JRASERVER-12891) was raised in 2007. That's 14 years ago. Atlassian clearly isn't interested in implementing this.
The current policy is anti-Agile and anti-Continuous Delivery - we need this implemented for Jira Data Center.
Version Manager for Jira is only available for Server also, so will need a solution for Data Centre as well.
Just adding it to the Permission Scheme area will be enough to be able to manage this access.
I fixed this problem by using this add-on application:
https://marketplace.atlassian.com/apps/1214929/version-manager-for-jira?hosting=server&tab=overview
But I sure do wish it became a native solution, since I would prefer to do all the Version creation and editing in the Releases tab, instead of a separate "Manage Versions" tab.
How long can be status "gathering interest"? It is already 1 year old issue. Please resolve it in next release.
Some of our teams automate marking a version released with build automation. It's worrying that we have to grant the build user project administrator in Jira to do so, when it would be much better if we could add a build user role that only has that power.
It's common for devs to manage their own deployments and versions these days, especially with Continuous Delivery and other similar strategies... Having the devs create new version iterations themselves is essential - it doesn't make sense to couple this function with full project administration though... 
Please can this be looked at?
We still waiting for this separated permission (version creation) for Jira Server. Version Manager don't have ability to create version directly from version field and user will need to go to another tab and first create version than go back to issue. This are too much unnecessary actions.
Hi everyone,
I found this marketplace app which solves this exact issue:
I just had to grant Administrator access to a bunch of developers for the single purpose of enabling them to create new versions/releases. Am I happy about that?? Nope! Atlassian, this request should be a no-brainer.....
This would be pretty useful to us, too. Is this anything that we can do to help to make this happen?
Thats exactly what we need: The delevoper should have permission to create new versions, but no further admin permissions
Vote!