IN jira creation form we want multi level select list along with a parent having multiple children

[syed_ahmed]

Basically we can get multi level cascading select list with the ALtassian  plug in called cascading custom fields. What we are unable to do is get  multiiple children of a parent with different types of fields in a cascaded fashion. BAsically the parent field is a drop down and the child field is a drop down and 3  different text boxes - Can we get help on getting another plugin to do this ?

[Christos Markoulatos -Relational-]

Hi @syed_ahmed 

If I understand what you're trying to achieve correctly, you want a parent field on the issue creation form (by creation form i assume you mean the JSM customer portal) that, depending on its value, reveals a child dropdown plus three text boxes, not just another cascading dropdown. For that scenario on Jira Cloud the best fit, as far as I know, is Extension for Jira Service Management by Deviniti, specifically its Dynamic Forms feature on the customer portal. You add the parent and the four children as Dynamic Fields on the same request type, then configure Field conditions on each child that reference the parent's value, with the child only appearing when the condition is met.

There's also something I wanted to flag proactively that you didn't ask about, but is worth knowing if your parent field is (or might become) an Assets object field. Conditional logic driven by Assets specifically needs an app since the native portal Forms conditional triggers don't include Assets as a supported type. Extension for JSM does support Assets object fields as a master field in Field conditions, with operators like contains object, contains any object, and not empty. If you ever want to filter a downstream Assets field's options based on an earlier selection rather than just show or hide it, that's their AQL settings feature, which sits in the Advanced edition of the app.

A couple of practical constraints to plan around. Conditions can only reference other Dynamic Fields rather than any field defined in the request type, and the very first Dynamic Field on the form can only carry User conditions (group-based), not Field conditions, so the parent has to sit first and the children below it, which matches the structure you want anyway. Changes to Assets configurations also sync every five minutes rather than instantly, so allow for that when testing.

Best next step is to start a free trial of Extension on a sandbox JSM space, set up the parent and four children as Dynamic Fields, and configure the conditions there before touching production. If anything specific to your field setup doesn't behave as expected, Deviniti's support is reachable directly from the Marketplace listing.

Hope this helps!

Helpful links:

• Extension for Jira Service Management on the Marketplace: https://marketplace.atlassian.com/apps/1212161/extension-for-jira-service-management
• Dynamic Forms overview: https://deviniti.com/support/addon/cloud/extension/latest/dynamic-forms/
• Configure Conditions (field types and operators, including Assets): https://deviniti.com/support/addon/cloud/extension/latest/configure-conditions/
• Dynamic Forms with Assets: https://deviniti.com/support/addon/cloud/extension/latest/dynamic-fields-with-assets/