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,360,221
Community Members
 
Community Events
168
Community Groups

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.

 

Capture.PNG

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

0 votes
Answer accepted

The new feature of Database Picker in Scriptrunner 6.6.0 provided a solution for this.

Suggest an answer

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

Online AMA this week: Your project management questions answered by Jira Design Lead James Rotanson

We know that great teams require amazing project management chops. It's no surprise that great teams who use Jira have strong project managers, effective workflows, and secrets that bring planning ...

190 views 1 6
Read article

Atlassian Community Events