Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

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

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?

19 answers

1 accepted

25 votes
Answer accepted


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.

Maybe it is fine for you


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

Like # people like this

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.  

Like # people like this

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?

Like # people like this

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?

Like # people like this

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. 

Like # people like this

Yes, please.

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

Like # people like this

+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. 

Like # people like this

Voting for this also

Like # people like this

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

Like # people like this

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.

Like Dave Lewis likes this

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. :-(

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

Like MiraGIP likes this


Like Dave Lewis likes this
Deleted user Apr 30, 2021


Like Oğuzhan Kırlangıç likes this
Like Oğuzhan Kırlangıç likes this
Like Oğuzhan Kırlangıç likes this

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

Like Oğuzhan Kırlangıç likes this
Like Oğuzhan Kırlangıç likes this
Like Oğuzhan Kırlangıç likes this

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

Like # people like this
Like Oğuzhan Kırlangıç likes this
Like Oğuzhan Kırlangıç likes this
Like Oğuzhan Kırlangıç likes this
Like Oğuzhan Kırlangıç likes this
Like Oğuzhan Kırlangıç likes this


Like Oğuzhan Kırlangıç likes this

+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

Like Oğuzhan Kırlangıç likes this

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

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!)  :) 

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


Like # people like this

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

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

Agreed, this gives more than needed.

I voted for it!

we are too!

Like Oğuzhan Kırlangıç likes this
Like Oğuzhan Kırlangıç likes this


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

Like # people like this

+1 This is a must-have!

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.

Thanks for sharing this!

Hello @Rafael Braga 

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

+1 for Jira Cloud

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

+1 Seems like a low hanging fruit to implement. 



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. 

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)

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>"

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

def create_fixversion(single_date):
response =
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):

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

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

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

The same issue with creating Components!

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

+1 for JIRA server

we need this too

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.

this is not for free

Hi @Mateusz Przybyłek ,

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

anythign available for server? 

well... not free anymore! :P

Suggest an answer

Log in or Sign up to answer