Create cascading custm fields options with automation

[Evgenii Pereverzev]

Hello everyone,

Case:

Have cascading field with values for example: 

Option1:

• Environment
• Infrastructure

Option2:

• Factory
• Management
• Design
• Production

Question:

Is it possible to have request type where user select option1 or Option 2, enters simple value and automation creates option for selected customfield context

[Cassie the Jira Mechanic · Accepted solution]

@Evgenii Pereverzev 
Hey there I believe you are referring to select list cascading fields. Below I will outline how to achieve this and use these field types. 



If that is the case you can use automation to fire off of which option is selected or isn't selected. That being said you would need the field ID, Parent option ID and child option ID to reference when doing your if / else statements.
There are admittedly many ways to find these IDs but I find the quickest easy way for someone new to all of this is to open up the field they are interested in the Jira Admin settings. Then once the field is open you would act as if you are creating new options or a new context.


After you click on that in the URL it actually shows the field ID.

Then to see the Parent option IDs you just want to make sure you are in the "edit parent select list" and then click edit next to the parent you wish to see.


Once you do you will again see the parent option ID in the url.


If you want to see the child option ID you would instead change "edit parent select list" to the parent that the child option is under in this case we are going to look at "this is parent 1" so we can get the ID of one of the child options.


 Then you will select "edit" to the right of the child option you want to see. When you do you will see the child ID in the url


Now that you have the details you need you can action automation. You can use it like any other field JQL wise ( if you are unsure act like you are making a filter using advanced settings and then build the JQL there to help you with suggesting. )




If this works out for you please report back and accept this answer so it can help others!





Bonus content:

You can also use advance settings and JSON for editing a cascading field.
Just support in the how this is the JSON format for this type of field.

More information on the JSON can be found here:
Advanced field editing using JSON | Cloud automation Cloud | Atlassian Support

[Joseph Chung Yin]

@Evgenii Pereverzev -

Need further clarification - Are you asking the 2nd option (child option of a parent option against a cascade select field) to be populated by the system and not the user (customer)?  So, customers/users only select the parent option when he/she creates the issue via the portal?

Please advise, so we can further assist you.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

[Evgenii Pereverzev]

Would like let user select parent and enter ticket summary.

Automation should create option for that parent with summary as value

[Joseph Chung Yin]

@Evgenii Pereverzev -

In Jira/JSM env, a custom cascade select field's parent/child options are pre-configured when you create the field.  You cannot use automation to populate the new child option (i.e. using the summary as the value) if it is not already defined in the field's context setup.

Secondly, when you expose the field in the request type form via the portal, customer can always populate the child value at will even though by default it is optional.

Sorry.

Best, Joseph

[Evgenii Pereverzev]

Im already successfully creating parent with http request in automation with this endpoint:

https://test.atlassian.net/rest/api/2/field/customfield_10068/context/10172/option

Im trying to figure out which endpoint should be used for child