-
Suggestion
-
Resolution: Unresolved
-
0
-
Problem summary
The Select List (cascading) field type is currently not supported in Automation for Jira.
Workaround
Workaround from https://support.atlassian.com/jira-software-cloud/docs/advanced-field-editing-json/#field-syntax-examples:
{
"fields": {
"First Field" : { "value": "First value", "child": { "value" : "Child value"} }
}
}
To copy values from the Select list (Cascading):
{
"update": {
"Cascading": [
{
"set": {
"value": "{{triggerIssue.fields.Cascading.value}}",
"child": {
"value": "{{triggerIssue.fields.Cascading.child.value}}"
}
}
}
]
}
}
- is duplicated by
-
AUTO-1207 The isEmpty/isNotEmpty functions don't work for empty cascading list fields
-
- Closed
-
-
- Closed
-
- Closed
-
- Closed
-
- Closed
- relates to
-
- Closed
- links to
[AUTO-131] The Select List (cascading) field type is currently not supported in Automation for Jira for multiple operations
Just attempted to create an automation with an Issue Fields Condition (if/then/else) on a cascading field...
....which I'm just now discovering isn't possible 
I'll have to redesign my entire solution now 
(including a whole meeting with the project owner about redefining their process)
Its really necessary to use cascading fields in automation. Please check this request
So this request is so we don't have to use the workaround of a "Compare two values" condition with poorly documented Smart Values for Cascading Select fields, right? (Hey guys, good documentation would go a LONG WAY)
{{issue.Your field name.value}}:{{issue.Your field name.child.value}}
EQUALS
Parent value:Child value
I am amazed as usual how Atlassian releases features that do not support scaling.
Cascading fields is amazing on its own, BUT if you cannot transfer the value to another ticket and it fails in automation to pick the value up to related/linked issues... It is not really well done. Really needs this to be solved.
I tried the above "solution", but this do not not work for non-parent issues. Linked issues do not get the value.