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.
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.
Scriptrunner with Service Desk Portal: Best practice to populate options based on two other fields?
I'm trying to make a application portal where users can apply for privileges. There are three fields: System, Department, and Privileges. The user selects what System they want to use, what Department they come from, and the Privileges field should search the database with System and Department as input, then populate the options with a list of Privileges available to that user.
So I set up two database pickers for System and Department, then I wrote two behaviours on both System and Departments. When either of them is updated, the behaviours turn the Privileges field into a multi select, query the database from a REST endpoint, and finally populate the options with the result from the query.
But I think this is way too complicated, and sometimes after I refresh the portal the behaviour cannot be triggered. Are there better ways to do this?
1 answer
1 accepted
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.