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!


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

Scriptrunner behaviour for limiting assignee list

Deleted user Jun 06, 2019

Hello everyone

This has been asked quite a lot already but I was unable to find an appropriate solution for our use case.

I really only need a behaviour which will run on all projects on all issuetypes and on every screen.

This behaviour should remove some options from the assignee field.

We cannot do this with the assignable user permission as these users should be able to be assignees but just not at every point and we would like to prevent our users from manually selecting them.

I also found the option of using a workflow validator but then again, after creation of the issue, the user could just edit the issue and then re-assign it which is why a behaviour would work best.

Can anyone help us out here on where to begin with this?


1 answer

0 votes
Peter-Dave Sheehan
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jun 19, 2019

I don't think scriptrunner behavior setFieldOptions() method can run on the assignee (or any user fields) to limit the available list.

At best, you can react to change in the assignee field and validate the value with the behavior and use the setError() method to stop users from saving while an invalid user is selected.

def okList = ['user1','user2']
def fld = getFieldById(getFieldChanged())
if(fld.value in okList){
} else {
fld.setError("Not a valid assignee. Pick from $okList")

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events