Support for managing field options in Behaviours#102

As a ScriptRunner Admin,
I would like the right users to view the appropriate options in a field,
So that they select the correct info, making the data more reliable and less confusing

Pleaes comment with detailed use cases - they are very helpful!

In our organization, we have used the DC behaviors for managing field options depending on issue type or other custom fields for many projects. So we are looking for the same behavior support in cloud as well. We are in the process of cloud migration. This is extremely important feature for us.

We use this feature to limit the option in the issuefield based on other selection on other field. (one of the example–> Components – in DC side we use to hide component from User that are used internally by service desk team). This is extermely important feature that help user and service desk team.

Update
Hello All! This feature has been released and you may filter down options based on your condition on the following supported fields in Behaviours: Priority system field, Select List custom fields, Multi-Select List custom fields and Checkbox custom fields!!

We are working with Atlassian to include more fields for field option support (like the Component field) and will continue to update you.

Please see our documentation for the most up to date details on what’s supported in Behaviours https://docs.adaptavist.com/sr4jc/latest/features/behaviours#behaviours-supported-functions

@Jpatterson - is it possible to priortize adding Component feild in next ? ( much appricated since that will elevate one of the major paint point for us … additionally in jira cloud we can’t now hide decomm components too)

Hi All! Please comment with your specific use case and specific field you need supported. This will help us get them prioritised with Atlassian and we can only build on what they make available to us. ( @RP thanks, got your request!)