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 to copy values of 2 select list (single choice) fields into Cascading field?

Sandra Meessen

Hello,

How do I get the values of my 2 existing custom fields of type "select list (single choice)" into 1 new custom field of type "select list (cascading)"?

So cfA into the parent part of the cascading field and cfB into the child part of the cascading field.

Thank you!

Accepted answers

Matthias Gaiser _K15t_

Hi Sandra,

I believe, this is something which you have to do manually via the Jira UI.

Another important question might be: Do you want to have cfB as child option for every parent option in the cascading field? If yes, I'd rathher recommend not to switch to a cascading select field.

Why do you want to convert them?

Cheers,
Matthias.

All comments

Matthias Gaiser _K15t_

Hi Sandra,

I believe, this is something which you have to do manually via the Jira UI.

Another important question might be: Do you want to have cfB as child option for every parent option in the cascading field? If yes, I'd rathher recommend not to switch to a cascading select field.

Why do you want to convert them?

Cheers,
Matthias.

unknown

Hi @Sandra Meessen,

You should be able to achieve the required functionality using the Script Runner Behaviors app.

Here is the reference document.

Hope this helps!!

Regards,

Priyanka

Sandra Meessen

Hi Matthias, Sorry it took me so long to respond, but my question is still valid.

Situation is: now I have 2 separate custom fields, both of type Select Single Choice: Customer and Projectcode. They are related, only a small set of projectcodes is applicable for a customer. Now I do not have a check between both, so values can be incorrect.

My solution to this issue would be: create a new custom field of type Select Cascading (call it Projectcode per Customer) where the parent part is the Customer and the child part is the Projectcode. This makes the 2 current fields obsolete and they can be removed from the screens (values are kept and can be filtered on. Correct?).

For issues created since implementation of that, it works in one go.

For existing issues I would like to migrate the value in the Customer field to the parent part of the cascading field and the value in the Projectcode field to the child part of the cascading field. Can I do this? Via bulk change? Or other way? Thank you!

Welcome!

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

Quick Links

Find more posts tagged with

jira

cascading-select