Add value Cascading List Automation

[Marcelo Ignacio Cid Abud]

I am trying to create an automation that adds a value (cascade list) to a ticket when it goes from the backlog state to in progress but I have not been successful.

The first choice is a bug and the second is an incident
Try this way:

{
"fields":
{
"customfield_10882": {
"value": "{{customfield_14967}}",
"children": {
"value": "{{customfield_15052}}"
}
}
}
}

Can anybody help me ?

[Bill Sheboy · Accepted solution]

Hi @Marcelo Ignacio Cid Abud -- Welcome to the Atlassian Community!

You seem to be matching the how-to from the documentation: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Cascading-select-custom-field

However, depending upon the field types/values you may need to reference the correct attributes.  Please see this similar post's question for an example: 

https://community.atlassian.com/t5/Jira-Software-questions/Re-Jira-Automation-Cloud-Cascading-Fields-Copied-from/qaq-p/2030873/comment-id/196924#M196924

Kind regards,
Bill

[Marcelo Ignacio Cid Abud]

Hi @Bill Sheboy 

I tray with both link but i had no results.

What I am trying to do is that when an issuetype "bug" is created, automatically the field "category by type of issue" (which is the drop-down list with several options) automatically complete the field assigning the option Bug -> Incident

[Bill Sheboy]

I am a bit confused by what you are trying, as you note triggering on the issue create and then seem to reference other fields in the JSON edit.

Would you please post images of your complete rule and the audit log details showing the execution?  That may provide more context.

And also, it is possible the edit is using the incorrect values.  Please try this:

• find an example issue (bug) which as the fields manually set correctly
• use the information in this how-to article to look at all of the smart values for that issue, and compare them to what you are trying to set in the rule for the cascading field: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

[Marcelo Ignacio Cid Abud]

Hi, 

This is my rule

{
  "fields": {
    "project": { 
      "key": "REST"
     },
    "summary": "Issue created from REST API",
    "issue type": {
      "id": "1"
     },
    "customfield_10300": {
      "value": "Bug",
      "child": {
        "value": "Incident"
      }
    }
  }
}

[Bill Sheboy]

Thanks for that additional information.

When you are only trying to set that custom field, you do not need any of those other fields.  Please note the error message in the log shows you are trying to change the project, which is not needed for this rule.  Instead please try this:

{
  "fields": {
    "customfield_10300": {
      "value": "Bug",
      "child": {
        "value": "Incident"
      }
    }
  }
}

[Marcelo Ignacio Cid Abud]

@Bill Sheboy Thanks 

The command worked perfectly for me, thank you very much.

[Bill Sheboy]

I am glad to learn that worked.  Please consider marking this question as "answered" to help others searching for solutions find them faster.  Thanks!