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 ?

[Olha Yevdokymova_SaaSJet]

Hi @syed_ahmed 

Native Jira cascading fields are useful when you need a parent → child relationship, for example:

• Parent: Department

• Child: HR / IT / Finance

But they usually become limiting when the “child” level is not just one dropdown, but a whole set of different fields — for example, one dropdown plus several text fields that should appear only for a specific parent selection.

For that scenario, I’d look at it less as a cascading custom field problem and more as a dynamic form logic problem.

If you are already using Jira Service Management Forms, I’d first check whether native form logic can cover this. For a basic setup like:

• Parent dropdown = Hardware
• Then show child dropdown + 3 related text fields

native JSM form logic may be enough, because this is more of a conditional form layout than a classic cascading custom field setup.

Where native cascading fields usually fall short is when you expect the child level to behave like a more complex group of different fields rather than one dependent select list. In that case, using form logic is usually the better direction.

If you need more flexibility than native JSM Forms provide, another approach you might consider is Smart Forms for Jira, developed by my team. It lets you build dynamic Jira intake forms where a parent dropdown can show different groups of child fields — dropdowns, text fields, attachments, dates, numeric fields, and more.

For example:

• If “Hardware” is selected → show device type, serial number, location, and justification
• If “Software” is selected → show application, license details, business reason, and approval contact
• If “Access” is selected → show system, user email, access level, and duration

This can also be useful if you need to map submitted values into Jira fields, create Jira work items from the form, share the form externally, or reuse the same intake flow outside the JSM portal.

Also, we’re releasing advanced form logic this month, which will support more than 15 conditions and the ability to group conditions into condition groups. That should help with more complex cases where one parent answer needs to control several dependent fields or sections.

So, if the requirement is strictly “one parent and one child select list,” native cascading fields may be enough. 

[Monika Ambrozowicz_Seibert_]

Hi @syed_ahmed it seems you should be able to do with with another marketplace app, called Awesome Custom Fields. Full disclosure: I am affiliated with the team. 

Awesome Custom Fields supports unlimited cascading levels (so you can go parent → child → grandchild and beyond), and each level can be configured as a single select, multi-select, or include a free-text note field alongside the dropdown. So for your case - a parent dropdown, a child dropdown, and additional text input fields - you'd be able to get much closer to what you're describing than the native field allows. The free-text component is attached per level rather than being three fully independent text boxes, so it's worth testing whether that covers your exact layout.

The app also works in JSM request forms and portals if that matters for your setup, and the cascading select values support JQL and Jira Automation.

If you want to try it out and see whether the field structure matches your requirements, the app has a free trial on the Marketplace. 

Let me know if you have questions about how the field types are configured, I'd be happy to go into more detail.

[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/