Issue Summary

At the moment, Cascading custom field is not supported via Automation as mentioned on this Feature Request, so in order to copy values to a new ticket, it's necessary to use Additional fields using the following JSON:

{
  "update": {
    "Cascading": [
      {
        "set": {
          "value": "{{triggerIssue.fields.Cascading.value}}",
          "child": {
            "value": "{{triggerIssue.fields.Cascading.child.value}}"
          }
        }
      }
    ]
  }
}

When using the Automation to raise a Service request and using the JSON to copy the values from the Cascading field, if the Cascading field is required, the Automation will fail and it will show the following:

Your request could not be created. Please check the fields have been correctly filled in. Please provide a value for the required field 'Cascading'

If the field is not required on the Request form, it will then create the request, but the Cascading field will be empty even though the Automation show as successful.

Using the Create Issue action (that won't set a request type), will set the value of the Cascading field correctly.

Steps to Reproduce

1. Create an Automation rule to trigger when an issue is transitioned and add make sure the Cascading field is present on the transition screen.
2. Add the Action to Create a Service Request and set to copy the Summary and Description and also set the Raise this request on behalf of for Customer created by this rule.
3. Expand the More options and use the JSON mentioned above using the name of the cascading field on your instance.
4. Create an issue and transition it to trigger the automation and during the transition, set the parent and child value of the Cascading custom field.

Expected Results

The Service request is created correctly and the fields are set.

Actual Results

The automation creates the Service request, but the Cascading field will be empty.

Adding a log action to the rule will show the values correctly on the audit log, but on the newly created ticket, it will be empty.

Workaround

Change the action from Create a service request to Create issue and use a Branch rule/related issues to edit the Request type.