...
Multi Level Cascade Select field is not officially supported by Adaptavist Script Runner plugin and its component. In case of a Script Runner Behaviour though, it is possible to apply a workaround that will allow to evaluate MLCS values using Behaviours even if the field is not supported.
Here below, we're going to see how to hide fields depending on the value selected of the first level of your MLCS field. The main idea is to trigger, via script, a "change" event on a field supported by Behaviours and to create then a Behaviour that handles everything we want to accomplish.
1) For our purposes, let's define two the following fields: one is
- a Multi Level Cascade Select field called "Department" and has an ID of 10100
- with three options on the first level
- a text field called "Employee" and has an ID of 11300
- (this field will be used for the workaround
- three Group Picker fields to assign an OnCall Team to the Issue, one for each option of the "Department" field. Depending on the first-level value of "Department", one of these fields will be shown
2) On the form (create / edit / transition screen) you'd like your Behaviour to be ran, choose one of the fields available and in the its own Field Configuration (related to the Project and Issue Type desired) add this javascript
...