nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

When a custom cascading field is updated, use an automation to edit another custom field

Mireya Cintora

Hi, I do not have any experience with using JSON as a FYI! We created two custom cascading fields to replace our custom short text fields (Facility Sandbox & Payer). With that though we needed to update our automation rules that involved those two short text fields, but the only way to use cascading fields in an automation is using JSON, at least that what rules said.

Can someone help me create that JSON coding to add to the 'More Options' section of the automation? I grabbed the custom field IDs of the two new cascading fields to get started..

customfield_12256 (R&D Facility)
customfield_12248 (R&D Payer)

Accepted answers

Bill Sheboy

Hi @Mireya Cintora

For a cascading field, you set both the "parent" and "child" values at once with JSON:

https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Cascading-select-custom-field

For example:

{
  "fields": {
    "customfield_12345" : { 
      "value": "parent_option1", 
      "child": { 
        "value" : "p1_child1"
      } 
    }
  }
}

However, your case seems more complicated as you appear to be mapping Short Text fields (Facility Sandbox & Payer) to the cascade ones with parent / child values.

Depending upon how many values are involved, you could use conditional expressions or lookup tables to help generate the JSON needed for each field.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Mireya Cintora

For a cascading field, you set both the "parent" and "child" values at once with JSON:

https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Cascading-select-custom-field

For example:

{
  "fields": {
    "customfield_12345" : { 
      "value": "parent_option1", 
      "child": { 
        "value" : "p1_child1"
      } 
    }
  }
}

However, your case seems more complicated as you appear to be mapping Short Text fields (Facility Sandbox & Payer) to the cascade ones with parent / child values.

Depending upon how many values are involved, you could use conditional expressions or lookup tables to help generate the JSON needed for each field.

Kind regards,
Bill

John Funk

Hi Mireya,

What is the use case? What exactly are you trying to do? When I update this field, I want to update this other field with this value ... etc.

Mireya Cintora

So when I update the the cascading fields R&D Facility and R&D Payer on the Epic, I would like it to update the cascading fields R&D Facility and R&D Payer on the children work types and sub-tasks.

Mireya Cintora

Sorry for confusion, the screenshots are the original automation that needs adjustments. So what I need to be done is when the cascading fields R&D Facility and R&D Payer on the Epic are changed/updated, I would like it to update the cascading fields R&D Facility and R&D Payer on the children work types and sub-tasks.

Bill Sheboy

Thank you for that information, and...

I recommend moving the condition testing the trigger work item is an Epic outside of the groups, as it is common to both.

Then use this JSON expression, substituting in the custom field ID values for the two different fields:

{
  "fields": {
    "customfield_12345" : { 
      "value": "{{triggerIssue.customfield_12345.value}}", 
      "child": { 
        "value" : "{{triggerIssue.customfield_12345.child.value}}"
      } 
    },
    "customfield_67890" : { 
      "value": "{{triggerIssue.customfield_67890.value}}", 
      "child": { 
        "value" : "{{triggerIssue.customfield_67890.child.value}}"
      } 
    }
  }
}

John Funk

See Bill's answer for syntax - I thought you might be updating a different type of field.

Mireya Cintora

So each group is split for:

1. Each Epic and its Children Work Types (Issue Type equals Epic)

2. Each Child Work Types and its sub-tasks (Issue Type does not equal Epic)

[Side note, originally I had this all under one since I wanted any change to the Epic would update the corresponding to all Children including the sub-tasks, but it wouldn't work so I split it up like so. ]

I tried but I am getting an error message? I am not entirely certain how JSON works but this is what I updated per your code above: Screenshot 2025-07-02 113755.png Screenshot 2025-07-02 113814.png

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management