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

How can I create a relationship between multiple select lists?

Rob Horan

I am on the hunt for a plugin that will let me establish a relationship between three fields in a way that will let me set up select lists for each field, and when a selection in field 1 is made I see a subset of field 2's options, and when a selection is made in field 2 I see a subset of field 3's options.

So Imagine:

Field 1 - General category (hardware, software)

Field 2 - Sub-category (Hardware options might be Monitor, keyboard, stress ball, etc. Software options could be Word, Jira, Photoshop, etc)

Field 3 - Symptom (For keyboards maybe keys stuck, not responding, etc. For Jira it could be workflow transition missing, etc)

The essence of this is the selection in Field 1 determines what options are available for field 2, and field 2's selection determines what options are available for Field 3.

If dynamic forms does this I will be happy.

If not, how can this be done in a way that is not a nightmare to maintain and is upgrade safe? Oh, and can be implemented by someone that doesn't know how to work with ScriptRunner. Just in case that's the only option.

Accepted answers

Ravi Sagar _Sparxsys_

Hi @Rob Horan

Have a look at Multi-Level Cascading Select.

Jira natively can't have 3 level (only 2 are supported).

I hope it helps.

Ravi

All comments

jira guy_ymfmzd

As far I know Script runner is the only option. It comes with behaviours component. You don't really need to know any scripting to do this

Ravi Sagar _Sparxsys_

Hi @Rob Horan

Have a look at Multi-Level Cascading Select.

Jira natively can't have 3 level (only 2 are supported).

I hope it helps.

Ravi

Andrew Laden

For a little bit of an outside the box solution. You can probably use CPrime's Database custom field, as it has the ability to parent/child relations in fields such that the parent can be used in the query of the child and updates dynamically.

You would have to keep your list of options in a separate database. (can use the same postgres server, but its own database with its own tables.) (This could be a pro or a con depending on your point of view.)

Rob Horan

YES! Perfect, thank you!

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server

app

dynamic-form