Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
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

How to control user-picker fields in Behaviors?

hi,

 

jira software 7.x was dynamically control the list of users in the user-picker field within the behaviors.

but, starting with jira software 8.x version, it seems impossible to control the user-picker field within the behaviors.

The list of users in the user-picker field should appear differently depending on the conditions, is there any other way?

 

Thank you.

1 answer

Hi @jyh0226_kicco_com 

To answer your question, you can easily update the user picker based on another field's value using the Behaviour.

Below is a sample working code for your reference:-

def optionsField = getFieldById(fieldChanged)
def optionsValue = optionsField.value.toString()

def userPicker = getFieldByName("User")

if(optionsValue == "DB") {
userPicker.setFormValue("admin")
} else if(optionsValue == "UI") {
userPicker.setFormValue("max")
} else if(optionsValue == "Web Service") {
userPicker.setFormValue("ram")
}

Please note this sample code is not 100% exact to your environment. Hence you will need to modify it accordingly.

You will need to use the Server-Side Behaviour for the code above. The Options field is a single select list, and the User field is a single user picker.

Below is a print screen of the sample behaviour configuration:-

behaviour_config.png

If the option selected is DB in the sample code above, automatically, the user field updates to Admin.

If the option changes to UI, the user is set to Max.

Finally, if the option selected is Web Service, the user field changes to Ram.

I hope this helps to solve your question :)

Thank you and Kind Regards,

Ram

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

ThinkTilt is joining the Atlassian Family!

This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...

267 views 16 17
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