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

Behaviour using multiple fields should filter one field

Hi community.

Please help me to select approach to creating Behaviours.

I need to filter possible values in field Priority. The field is custom.
It depends on Issue type, Customer (customfield), Product (customfield).

I'm looking at option to create one Behaviour which will have a script for each of this three fields. What are your thoughts? 

Or maybe anyone has suggestions that can save me some time?


2 answers

1 vote

Seems like you would need the same script on all 3 fields so that changing each field triggers a recalculation of your priority.

The best way to achieve that would be to store a script in your script root and point to the script from each server-side script for each field in the behavior. This way, you only have 1 piece of code to maintain.

Hi Peter, 

You are right that 1 piece of code is much better than several.
What do you mean by ' script root '? I am using behaviour. So the script should be located in Behaviour Settings in Initializer part?

Or may be It is better to have 3 bihaviours, like one behavior for one field.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events