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

Cascading select field: Keep child selection on parent change

Moritz Wagner

Hello,

We're using the cascading select field as a "Matrix input" meaning each parent selection has the same child selections. Is is somehow possible with scriptrunner behaviours, to keep the selected child index selected, when the user changes the parent selection?

Or is there another possibility to simply have a matrix like input field?

Thanks!

Accepted answers

All comments

Payne

If each parent has the same children, why use a cascading select field, and not simply 2 select fields?

Moritz Wagner

Because Jira cannot display 2 fields in one line in edit screens and for the issue view two fields take a ridiculous amount of space compared to the cascading select method. That's the only reason to be honest.

Nic Brough -Adaptavist-

No, you can't do this. Each "child" option in a cascading select belongs to its "parent" option. Keeping a child selected when changing the parent is nonsense, because it would no longer be a valid selection. (Technically, you could get Behaviours to do this on the surface, but then Jira will refuse to save the result because it's nonsense)

You should move to using two separate select lists if you need this sort of matrix.

Moritz Wagner

I know the mechanics, and I know that It's a workaround, but since Jira is so limited, we need these workaround. It sure makes no sense when programming, but with jira these kinds of things are necessary to save you from loads of buggy plugins sadly.

Whatever, luckily our users can manage it themselves, until I find a way to fix it.

I'll post the working "nonsense" later in here.

Nic Brough -Adaptavist-

So you're trying to bodge something that leads to presenting invalid data to your humans, who will then have to correct it before they can commit a change? Why put them in that position?

Moritz Wagner

Your fellow Payne did understand the use case correctly, you seem to miss it a little. No invalid data, and no correction anywhere just a simple automatism that helps the user. Just wait and maybe I get it to work to show you, so you know what I mean.

Welcome!

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

Quick Links

Find more posts tagged with

scriptrunner

jira-software