Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

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.

https://scriptrunner.adaptavist.com/5.2.0/jira/recipes/behaviours/restricting-priority-and-resolution.html#_restrict_priorities_by_group

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
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

321 views 9 7
Read article

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