How do I assign the permission to create Versions to a permission scheme without granting admin?

[Matt Cook]

I have a lead developer that i need to have access to create new versions within a project. I've found that currently the only way to do this is to grant them a Jira-Admin privilage. 

I want to be able to give them the ability to create a new version, but without having to grant them a full admin permission.

Is this possible?

[Alexey Matveev · Accepted solution]

Hello,

You need to grant  the lead developer Administer project permission, not Jira admin permission. It is different. You can see here what a user with Administer project permission can do. https://confluence.atlassian.com/adminjiraserver073/managing-project-permissions-861253293.html

Maybe it is fine for you

[Matt Cook]

Thanks

This gives more than I was hoping it would but it's fine for what I need. I'll maybe suggest a feature request to break down permissions on a more granular basis

Thanks for your help

[Joel]

I agree with Matt here, permissions need to be more granular than this. We have a team specific to managing releases at an enterprise level. Having that team able to manipulate all projects that utilize the release system at an Admin level project to project is way too much access all at once.  

[Ben Bloodworth]

My team is also dealing with this problem.  We want to give someone with limited permissions access to create versions, but they do not need to be administering the whole project.  Has there been any movement toward more granular permissions for this.  Is there somewhere where I can submit a change request to Atlassian for this?

[Paul Preibisch]

I also agree with this.  We want to give the product manager the ability to create versions - why should we give them the ability to manage the entire project?

[Digital Commodore]

Throwing another "me, too!" in here- it's fine to keep top-level permission "switches", but we should also have the ability to give these permissions piecemeal. 

[Peter Kaiser _Admin_]

me too :-) 

[Evan Wolf]

Yes, please.

[Mark Ward]

Yes, +1, this definitely needs to be more granular!

[Ciarán Lyons]

+1 on this.

[Rafael Braga]

+1, I just want a Developer to be able to create versions. He shouldn't be fiddling with my workflows. It just doesn't make any sense. 

[Tamas Zakanyi]

Voting for this also

[Tal Arbel [Administrator]]

Same here

[Tobias]

Please also vote the issue https://jira.atlassian.com/browse/JSWCLOUD-17608 

[Martin Perry]

How is this not changed yet? Granting project admin just to make a new version is overkill.

[Thomas Legrand]

+1

[Howard Olson]

There is a pretty rich set of granular options for determine permissions for users, roles, groups, etc.  Seems odd to me that this one was left off the list.  We need it.

[StephanieC]

We are going through the same thing. When we launched in 2016, we were told to keep all tickets open for everyone to see and that noone but PMs and managers would EVER add components and fix versions. Things changed (of course) and now we only have one permission scheme that goes across all maintenance projects and we will have to completely re-design permission structure just to make  "X" project only permissions a thing. :-(

[hosssamezzoukh]

here the same

[Furkan Salkım]

+1

[DWedekind]

+1

[Stefan Pröll]

+1

[Marcus Atkins]

+1

[Robert Reichel]

+1

[Jonas Sieber]

+1

[Jon Stuber]

+1

[Logan Chang]

+1

[Daniel Kimball]

+1

[Iurii Shcherbyna]

+1

[Rémi Lamotte]

+1

[Xavier Calvo]

+1

[Aleksey Vyazovsky]

+1

[william@perasotech.com]

+1

[Wouter Devolder]

+1

[Doug Hammond]

Same !

[Kate Krotova]

+1

[Lodewyk Duminy]

+1

[Millie Ryan]

+1

[Quintin Venter]

+1. It blocks so many systems that are a bit more advanced than someone working out of a garage.

[Shai Bhula]

+1 

[Rick Luo]

+1

[Chamara Henaka]

+1

[Sreeman Nalli]

+1

[Quang Lam]

+1

[Martin Galauner]

+1

[Erlend Flaa]

+1

[Jasdeep Singh]

+1

[Octavius Sylvers]

+100000

[Anthony Calce]

FIX ThiS NOW WE ALL NEED It!

[Deleted user]

+42

[Jira Admin]

+1

[Gustaf E]

+1 

[Kelvin Ekonomi]

+1

[Haneen Fayed]

+1

[KARIM BACHIRI]

+1

Thanks

[cnolan]

+1

@JiraAdmin 

[Karrie Smith]

+1

[Sotiris Christou]

Has anything changed whatsoever? Are we being listened or ignored?

[furseyev]

+1

[Ning]

+1

[Vincent Quiles]

+∞

[Pip Turner]

+1 - can't believe this was a feature requested nearly 5 years ago now!

[Bernhard Renner]

+1

[Bethanne Lamb]

+1

[bence_kocsmar]

+1

[Stefan Weiß]

+1

[u606360]

+1

[Artem Semenov]

+1

[Neel Singh]

+1

[Aaron Cook]

+1

[Yatish Madhav]

+1 - because why not :) and also it would be ideal to have this available as a granular permission rather than the full project admin permission. Thank you for the post and comments. I have voted and watched JSWCLOUD-17608  - thank you

[Ori Lazar]

+1

[René Verboon]

It's crazy that you need to be project admin to create versions. That creates a bottleneck and slows don the team.

[David Wolfman]

+1 Jira is horrible with lack of granularity. Love how this issue is going on since 2017 and we pay for the privilege of poor permissions and other capabilities that exist in every other application in the field.

[George Turnbull]

+1 more permission control!

[George Papidas]

+1

[Rosa M Fossi]

Has a suggestion ticket been created for this with Atlassian? I'd like to go up vote it, but I haven't located one.  If you know of one, post it here (if not, I'll go create one!)  :) 

[Corin]

I've just created one, hopefully you didn't too ;)

JSWCLOUD-17608

[Tobias]

Perfect, thank you @Corin! I vote for it. But, like most other issues from customers, Atlassian will ignore it. 😪

[Rosa M Fossi]

@Corin  I didn't get a chance yet.  I'll go vote it up!!

[Paul Wegmann]

Agreed, this gives more than needed.

[Page Partain]

I voted for it!

[Macsis]

we are too!

[Alan Dalley]

and me!

[Darja Odorovska]

+1

[Ioannis Drositis]

+1

[Jaroslav Klech]

+1

[Jonathan Haro]

+1

[Joc]

+1

[Cheng-Han Ly]

+1

Jira needs a Permission called Manage Version, to allow Versions to be created, changed, released, archived, without being project admin.

[Rahul Savaikar]

+1 Agreed

[Mark Noller]

+1 This is a must-have!

[Rafael Braga]

I've found a way to do it with Automation For Jira. You can create an automation that receives a post request, and that post request can create (and release) a new version. I made one of those and gave the URL to developer that was needing it. It works for me but it's a far cry from a perfect solution.

[Rosa M Fossi]

Thanks for sharing this!

[Rahul Savaikar]

Hello @Rafael Braga 

Could you please share the details of how you managed to (almost) achieve this  using Automation for JIRA?

[Alex Eije Saito]

+1 for Jira Cloud

[cnolan]

+1 Seems like a low hanging fruit to implement. 

[Cesar Ortiz Salazar]

Uno más, dos años después de que apareció el problema, aún no hay respuesta? :(

[Steve McG]

+1 from me too. I do wonder if anybody from Atlassian even bothers reading what the community asks for.

[George Turnbull]

I posted this answer for the question about a non-admin solution for Managing Versions (for with there is no Atlassian answer), but if you want a person to be able to create Releases AND manage Versions, you need both the permissions listed below:

The original Answer is only partially correct (at least for Data Center). Until Atlassian deigns to add this as a stand-alone permission, you need the following permissions on your project to fully manage Releases & Versions:

1. You must have the Administer Projects permission (with or without extended project administration). NOTE: This permission alone allows you to CREATE a Release AND add issues from the backlog to a version. It DOES NOT allow you to add an issue to a version in a Detail screen (neither the board Issue Detail View, the Edit dialog nor the Detail screen)

2. You must have the Resolve Issues permission. This will enable you to add an issue to a Version using the board Issue Detail View, the Edit dialog and the Detail screen.

For us this was critical as we often add issues after they are In Progress (no longer in the backlog.

Hope this helps clarify this rather confusing problem.

[Christian Slaviero]

+ 1

[Teri Smith]

+1

[Mike.Rooze]

+1

This should absolutely be fixed. In an R&D environment, we create many "versions" that are not going to a client, but rather an internal team of testers. Using a version (for affects version and fixed version) is absolutely critical for defect tracking. My Developers need no other functionality than this. There should be a separate permission to allow this level of access. 

[Anthony Calce]

LETS GO! Add this feature already... we're paying lots of money for this cloud solution, the very least you guys can do is listen to the things WE NEED and not waste time with forcing everyone to change their JIRA view (the new one sucks BTW)

[Richard Browne]

This annoyed me to no end, I decided to do something about it, I use dates for releases and I came up with this script:

This gives details on what the post request looks like and the auth that will generate FixVersions. In MY case, I have added logic to create a loop of fixVersions based on a range of dates.

Hope it helps, please comment if it does help

import requests
import json

from datetime import timedelta, date

# ************** SETUP ********************

# This is my email
MY_JIRA_SUPER_USER_EMAIL = "<my jira email>"

# Key needs to be generated by logging into Jira and creating an access key, not too difficult (I wouldn't share this though BTW)
MY_JIRA_KEY = "<my jira access key>"

# My Jira domain
MY_JIRA_DOMAIN = "<mycompany>.atlassian.net"

# ************** FUNCTIONS ********************

def create_fixversion(single_date):
response = requests.post(
"{}/rest/api/3/version".format(MY_JIRA_DOMAIN),
auth=(MY_JIRA_SUPER_USER_EMAIL, MY_JIRA_KEY),
headers = {'content-type': 'application/json', 'Accept': 'application/json'},
data = json.dumps(
{
"archived": False,
"releaseDate": single_date.strftime("%Y-%m-%d"),
"name": single_date.strftime("%Y-%m-%d"),
"description": single_date.strftime("%Y-%m-%d"),
"projectId": 11805,
"released": True
}
)
)

def daterange(start_date, end_date):
for n in range(int((end_date - start_date).days)):
yield start_date + timedelta(n)

# ************** RUNNING CODE BELOW ********************

# Change these for your date range
start_date = date(2021, 6, 30) # and including
end_date = date(2021, 7, 1) # and not including

# Loop through
for single_date in daterange(start_date, end_date):
print(single_date.strftime("%Y-%m-%d"))
create_fixversion(single_date)

[Aaron Ashworth]

Late to the party, but if you're still accepting +1's, here's mine.  :) 

[Stijn Maller]

Not sure it will make much difference, but let me add another +1

[MicroflownAVISA]

+1!
The same issue with creating Components!

Would be great if this could be configured like all the other authorization options in a project

[Kent Chiu]

+1 for JIRA server

[Adrian SMYTH]

we need this too

[Roey Shamir]

Hi, you are more than welcome to try my plugin for free - Version Manager for JIRA cloud.

Not only does it let you delegate the manage versions permission to whoever you decide but it also lets you assign components to versions.

[Mateusz Przybyłek]

this is not for free

[Roey Shamir]

Hi @Mateusz Przybyłek ,

Thanks for your reply. I'll clarify - you can try it for free in a 30-day trial.

[StephanieC]

anythign available for server? 

[Christos Moysiadis]

well... not free anymore! :P