It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Restricting issue creation of certain Issue Types based on user project role

Hi Team,

I just want to know, if there is a way to restrict creation of an issue type based on the Project Role.

For example,

I have 3 roles in my project,

  • Project Role Admin
  • Project Role Developer
  • Project Role User

And i have the below issue types,

  • Story
  • Epic
  • Bug
  • Task

I want only Project Role Developers to be able to create only Bug issue type.

Please let me know incase of more information required.

Thank You,

4 answers

1 accepted

Hey Surender!

Thanks for raising this question! :D

To clarify, are you saying that you want to limit the options for Developers so that they can ONLY select the "Bug" issue type?

After doing some digging, I'm afraid I've come back with some info that's more disconcerting than I would have hoped. As it turns out, the Issue Type field is one of the only fields that, using a Behaviour, you can't manipulate the selectable options for. This has been a long-standing issue and is recorded in SRJIRA-1010.

Although that throws out the cleanest solution, you could still implement essentially the same functionality with a ScriptRunner Behaviour. For instance, you can still set the Issue Type field. So you could use a Behaviour to check if the user is a Developer and then automatically set the field to "Bug" and lock it so that they cannot change the Issue Type. The code to do this would look something like:

import com.atlassian.jira.component.ComponentAccessor
import static com.atlassian.jira.issue.IssueFieldConstants.ISSUE_TYPE

// if the current user is in the Developer role only, set the issue type to "Bug", and lock it
def projectRoleManager = ComponentAccessor.getComponent(ProjectRoleManager)
def user = ComponentAccessor.jiraAuthenticationContext.user

def remoteUsersRoles = projectRoleManager.getProjectRoles(user, issueContext.projectObject)*.name
log.warn("Thing: "+remoteUsersRoles)
//Set "Project Role Developer" to the name of the project role that you'd like to check for
if (remoteUsersRoles == ["Project Role Developer"]) {
def constantsManager = ComponentAccessor.getConstantsManager()
def bugIssueType = constantsManager.getAllIssueTypeObjects().find{ == ["Bug"] }
//Set the issue type to Bug and make it read-only

There is also an example of setting the Issue Type in our documentation here.

Let me know if this solution would work for you or if we need to explore some other avenue. Also, if you need help implementing the above Behavior, give me a holler. :D



@Aidan Derossett _Adaptavist_I am trying to allow almost the opposite. If a user is a developer they can create issuetypes Task or Bug but not Epic. Any advice?


Hey Eric!

Sorry it took me so long to get back to you :(

If you want to restrict a particular role to two different issue-types, you may run into some trouble with the bug that I mentioned in the above comment. Unfortunately, as of right now you can't restrict the options that are available in the issue-type select list. So you'll have to implement some other method to get this same functionality.

For instance, you could write some custom JavaScript to do it for you and then inject it into JIRA using a ScriptRunner Web Resource. That's not the most trivial of tasks, but it would be the cleanest workaround. :)



0 votes
Peter DeWitt Community Leader Jan 09, 2018

@surender kallam, If you are using different workflows for each issuetype, you can use a validator on the issue creation link.  Jira suite utilities will allow you to validate against project roles.  Naked Jira may require specific user groups to be used.



Which validator should i choose , tehre are many options for validators

@Peter DeWitt and @Aidan Derossett _Adaptavist_, Even i am also raising the same query where I need to restrict a group or individual users for certain issue types.

I saw the above script and i can add them into scriptrunner, but I have a question here. Where can i call this script? How will this script help in restricting the group?

It would be greatest help if I get your guidance here.

thank you in advance

Is there any way to restrict on JIRA cloud. I'm using properties in the workflow to restrict his. Below is what I'm adding on JIRA creation:



Is this correct or is there any way around it.

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you