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

Restrict Priorities by Role

I'm looking for best way to only allow those with the project Administrator role to select the two highest priorities when creating or editing an Issue in my project. We have Critical, High, Medium, Low priorities, but only want normal users who submit tickets to select Medium and Low, but those with Project Administrators role can select any.

I found this Script Runner example, which mentions groups not roles, but I'm  a bit lost on where to use this code or how to modify it to work with roles instead of groups.

It was not clear where this code would be placed, would I add it as a Behaviour then map it to my project, or is it something I would add to a workflow transition?

I tried adding it as a behaviour but get syntax errors on these two lines


static com.atlassian.jira.issue.IssueFieldConstants.PRIORITY


def allowedPriorities = constantsManager.getPriorityObjects().findAll {

1 answer

I'm struggling with this myself, but I can tell you that it needs to be an initialiser

You would then add a mapping for your project and the issuetype(s) applicable

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events