Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

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
4,644,490
Community Members
 
Community Events
196
Community Groups

Querying Insight objects directly instead of via a custom field in a behaviors rule

Hi

I have a behaviors  rule that I currently have to manually enable/disable that controls visibility and mandatory nature of a text field.

I would prefer if I can make a server side script in this rule so that it checks directly against values in an Insight object so it can automatically hide/show the mandatory field if a regular user has changed the attribute value of the Insight object, this way I can always leave it running.

All groovy validators/conditions I've seen around Insight objects refer to checking against an Insight custom field. However, I need this to check directly on the object itself, as I need this beahviour rule to run at the create stage, at which point the read only Insight custom field won't have filled yet.

 

Does anyone have any example groovy code around checking directly against Insight object attributes?

 

Thanks

0 comments

Comment

Log in or Sign up to comment