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; } } }

Regarding Screens

sravani vennapusa_vueflh

I want to get fields as hierarchy in Jira screen as shown below: If i select field 1 i should get field A values and Field B values and respectively . If i select field B i should get field1, field2,field 3 values. How can i implement it in jira . Can someone suggest.

Accepted answers

All comments

Sebastian Krzewiński

Hi @sravani vennapusa

Jira out of the box don't provide solution for your case. I can suggest to use Script runner behaviour or Dynamic Forms for Jira.

Regards,

Seba

Marc -Devoteam-

Hi @sravani vennapusa

This is not possible ootb in Jira.

Only JSM has this capability using Forms on a portal.

Only option there is in Jira to use Cascading Select custom field where based on chosen parent value child values are available.

You could revert yourself to start using a 3rd party solution like Scriptrunner and start using behaviours that can achieve this kind of working.

sravani vennapusa_vueflh

But ScriptRunner on Jira Cloud cannot dynamically change dropdown options between two separate fields right? Is it possible?

Marc -Devoteam-

Hi @sravani vennapusa

No it can't That's also not what you are stating.

Create a behaviour based on options chosen in field a to show Field a or Field B

If the value is selected that will show Field B, based on the value chosen in B show field 1, 2 or 3

Arkadiusz Wroblewski

Hello @sravani vennapusa

What Jira gives you natively is a Cascading Select field, but that is only 2 levels inside one field parent and child. It does not cover the kind of structure from your sketch where one choice shows other separate fields and those fields then drive another level again.

Legit Options will be show/hide fields based on another selection, then ScriptRunner Behaviours can help there or build a true multi-level dependency across several fields, then I would look at a dedicated app very carefully, because Cloud still has UI limitations there. Adaptavist’s own Cloud docs also note that Behaviours are limited by Atlassian’s UI modifications support.

Wajdi from VIP.LEAN Solutions

Hi @sravani vennapusa

This use case should be possible using the powerful UI Modifications capabilities of the Atlassian Forge platform for Jira Software and Jira Work Management (And JSM announced recently).

If you are using ScriptRunner Behaviours, you should be able to implement this as well.

I tested exactly this setup with our own app, Behaviors Builder, and it worked very well (5..10 minutes of effort - with 0 Code lines), including additional option logic (hiding and showing).

You can see a demo here that shows exactly your setup:
https://app.supademo.com/showcase/cmj7csmfy00nj280ih9xtwude?demo=7&step=1

For transparency, I’m part of the company behind this app. There are certainly other apps and approaches available as well — this is just one possible solution.

Thanks & Best Regards
Wajdi

sravani vennapusa_vueflh

Is this possible on jira cloud? Can you please let me know.

Wajdi from VIP.LEAN Solutions

Hi @sravani vennapusa :

Yes, for sure - my demo was on Jira Cloud.

Here is the link to the document that lists all Atlassian Cloud capabilities for UI modification.

For more details about the Atlassian cloud capabilities—since various combinations of space types and field types result in different supported field modifications—we display only eligible combinations in your app. Feel free to ask if you need more information! :-)

BR, Wajdi

M Chandra Shekar

Hi @sravani vennapusa You can use a cascading select field, but it supports only two levels. For more than two levels, consider creating multiple cascading fields to achieve the structure.

Laura Campbell_Seibert

HI @sravani vennapusa As the others mentioned, this is not possible out of the box. But you can achieve it with a Marketplace app, for example Awesome Custom Fields. (I am with the company behind the app).

Here is what it would look like on JSM with the cascading select list from Awesome Custom Fields. You can add as many levels as you need.

M Chandra Shekar

Hi @Laura Campbell_Seibert

Thanks for sharing this. Good to know!

What I can suggest, if they are not ready to proceed with the above app, is the following: Steps:

1. Create two cascading fields:
Field 1 (Level 1)
Field 1 (Level 2)

2. For Field 1 (Level 1), add parent and child dropdowns.

Example:

Parent values: Field A and Field B
Child values:

Field A → Field A.1 and Field A.2
Field B → Field B.1

The output values will be:

Field A – Field A.1
Field B – Field B.1

3. For the second cascading field, Field 1 (Level 2), use "Field B – Field B.1" as the parent value and add "Field B.1.1" as the child value.

The final output will be:

Field B – Field B.1 – Field B.1.1

This way, we can achieve structure without relying on third party apps.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-cloud