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!


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

Suggest an answer

Log in or Sign up to 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

AUG Leaders

Atlassian Community Events