nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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?

Accepted answers

Alexey Matveev

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

All comments

Alexey Matveev

Hello,

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_usauwx

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?

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_9s7str

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

JSWCLOUD-17608

Tobias_c77xl0

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

Rafael Braga_1miiw8

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!

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_xoa9ub

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.

Adrian SMYTH

we need this too

StephanieC

anythign available for server?

Kent Chiu

+1 for JIRA server

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

Steve McG

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

Stijn Maller

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

Aaron Ashworth

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

Richard Browne_lkm5zz

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)

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)

Mike.Rooze

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.

Mark Noller

+1 This is a must-have!

Rahul Savaikar_qm2ff9

Hello @Rafael Braga

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

Cheng-Han Ly

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

Rahul Savaikar_qm2ff9

+1 Agreed

Cesar Ortiz Salazar

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

cnolan

+1 Seems like a low hanging fruit to implement.

Teri Smith

Alex Eije Saito

+1 for Jira Cloud

Christian Slaviero_xn1kqh

+ 1

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.

Marc Jay

I've found a working workaround with Automation. Use the "Manual trigger from issue" trigger, tick "Prompt for input when this rule is triggered" and add a Short Text field, then add a "Create version" action that uses the input from the trigger. The Version name would be something like (depending on your field name):

{{userInputs.versionName}}

Then anyone who has permission to run the action (defaults to everyone but you can restrict in the "Manual trigger" block) can kick off the automation from a ticket and create a version.

Ida Bagus Subagia

Hi, try this quick steps to assign a team member as project administrator so he/she will able to create Versions in the specified project:

Go to JIRA Administration > Projects
find project by using available filter
click the project name
go to left menu "User and Roles"
find a team member who will be assigned to be able to create Versions
set as Administrators, you can assign multiple roles e.g both as developers and Administrators

Yogesh Patil_ecyx9y

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

permission

version

security