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; } } }

Is there a way to restrict users from creating certain issue types on the backlog?

Shaquanna Chappelle

For some of our JIRA projects, we want to restrict our business users from adding stories/tasks to the backlog. However, we still want them to have the ability to create bugs during their UAT testing. Is this something we would have to do at the project level, or can this be done at the global setting level? I was thinking about creating a group with only certain permissions and adding those users to that group. Will that work?

Accepted answers

Niranjan

Hi @Shaquanna Chappelle ,

With script runner plugin, you can do so.

https://scriptrunner.adaptavist.com/6.9.0/jira/recipes/behaviours/restricting-issue-types.html#

Create a separate workflow that needs restriction and add a simple scripted validator in the workflow as below

To restrict it to a particular project role:

isUserMemberOfRole('Administrators')

To restrict it to a particular user group:

import com.atlassian.jira.component.ComponentAccessor

def groupManager = ComponentAccessor.getGroupManager()
groupManager.isUserInGroup(issue.reporter, 'business-users')

Nic Brough -Adaptavist-

I'm afraid there's no way to do this in Jira. There are some tricks you can play on Server with some apps, but Cloud only really has a couple of really clunky options for it.

You can't stop someone who has "create issue" in a project from starting to create an issue of any type in the project. But you could

Use automation or scripting to change it in a way that it does not get used (I'm not sure you can easily change the issue type, but you could put flags or warnings on it)
Use an impossible validator on the "create" transition - "if person not in developer group, then fail validation"

Both of these are clumsy - changing data that someone entered can be annoying to them, they may have been doing it for a good reason and you're changing that, and having someone enter a load of data only to be told "you can't do this" after clicking save is demoralising.

All comments

Niranjan

Hi @Shaquanna Chappelle ,

With script runner plugin, you can do so.

https://scriptrunner.adaptavist.com/6.9.0/jira/recipes/behaviours/restricting-issue-types.html#

Create a separate workflow that needs restriction and add a simple scripted validator in the workflow as below

To restrict it to a particular project role:

isUserMemberOfRole('Administrators')

To restrict it to a particular user group:

import com.atlassian.jira.component.ComponentAccessor

def groupManager = ComponentAccessor.getGroupManager()
groupManager.isUserInGroup(issue.reporter, 'business-users')

Nic Brough -Adaptavist-

I'm afraid there's no way to do this in Jira. There are some tricks you can play on Server with some apps, but Cloud only really has a couple of really clunky options for it.

You can't stop someone who has "create issue" in a project from starting to create an issue of any type in the project. But you could

Use automation or scripting to change it in a way that it does not get used (I'm not sure you can easily change the issue type, but you could put flags or warnings on it)
Use an impossible validator on the "create" transition - "if person not in developer group, then fail validation"

Shaquanna Chappelle

Thanks @Niranjan and @Nic Brough -Adaptavist- for your response!

As a follow up question, when configuring issue level security, this restriction is for what issues are visible to the user correct? It doesn't prevent users from creating specific issue types, right? It looks like for our use case, we would have to do some level of automation/scripting, so I just wanted to rule out any existing solutions first.

Thanks again for your help!

Nic Brough -Adaptavist-

Note that is Server only, it does not work on Cloud, which the post was about.

Nic Brough -Adaptavist-

Correct, you can create issues that you then cannot see because of the security level. It can't stop you creating the issue, just hides it.

Amir Katz (Outseer)

Using a validator 'if user is in role' does work, but the problem is that you cannot control the error message (it will be 'user is not in XYZ role').

What I did is use a validator provided by the JMWE add-on (not free, but worth the money) - the one called 'build-your-own (scripted) validator'.

In it, I specified an improbable condition (it can happen, but unlikely):

user.displayName == "There is no such user"

and set the error message to 'Creation of this issue type is deprecated!'

Amir Katz (Outseer)

All the hacks suggested in this thread will go away when Atlassian adds conditions to the Issue Create transition...

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

atl-gruland