Automation reference (Cloud)
- Andrea Pedrollo
Using Automation for Jira, you can set values of a Multi-Level Cascading Select custom field. As any other third-party custom field, you’ll need to use the “More option” text area to provide the values.
This is an example of a JSON object to pass (nested within the “fields“ object, required in Jira Automation).
{
"fields": {
"mlcs_field": "{\"lv0\": {\"label\": \"1\", \"value\": 2}, \"lv1\": {\"label\": \"1.1\", \"value\": 8}}"
}
}Explanation:
The JSON value passed comprehends the level of options and its labels and values. the escaping \" are necessary for Jira Automation to accept the values (' and ` are not allowed).
mlcs_field: The name of your custom field. Alternatively, you can use the field ID, such as customfield_10036.
label: Text string, represents the name of the option. This is what you will see of the selection made.
value: Number, the ID of the option.
There is a discrepancy in the names used to pass data to Automation and the names used by Jira to manage the MLCS options.
Automation for Jira | Graphql request |
|---|---|
Value | Id |
Label | Value |
Go to the MLCS Cloud app.
Anywhere on the page, right-click and select “inspect“. This will open the browser inspector.
Go to the Network tab and refresh the page (this is to make sure that the calls will be shown in the Network tab).
Filter the results by “graphql“ as shown in picture:
You’ll find a few “graphql“ requests. The one you’re looking for contains a list of all the available options, nested in “Data → invokeExtension → response”. This is what the response looks like:
