https://studio.atlassian.com/browse/JIM-231

Hello any news about this issue ?
We are unable to import data in cascading fields.
Thanks for your help.
François

We have same issue. I have a csv file with about 500+ artist names and their recording labels, which we want to import into a Label/Artist custom field (cascading select). Has anyone come up with any work around?

How did you get around the migration issue?? We are facing a similar data migration road block.

Regards
Amrut.

Since the csv import facility can't handle cascading selects, I thought perhaps I could generate a jelly script that would update the issues after they were imported. Sadly, this capability doesn't exist either!! If you create the issue using Jelly script, you can set a cascading select field as part of that operation, but there doesn't appear to be any way to update existing fields in an issue using Jelly script.

As a result, I'm left with the following options: 1) Manually edit hundreds of imported issues (assuming none of them are in a closed state), 2) bypass Jira and try to set the fields by interacting directly with the database, or 3) write my own import utility using java.

If anyone can think of any other alternatives, I'd be glad to hear it.

We have two source columns in our import field, but it makes the most sense to map them to a cascading select in Jira, to no avail.I wonder whether manipulation after the fact makes sense. (Laboriously: filter, mass change, filter, mass change)

Is there a database schema I can follow so I might engineer a work around of my own?

Has anyone come up with work around?

Hello,

We are trying to import a field into a cascading select list and are currently unable to due to this issue.

This failure is causing data loss for our imported bugs. (The field we are unable to import is our customer list. )

Thank you in advance.
Sincerely,
Ernie Benoit

Is this going to be resolved at some point. We are in a situation now where we really need this feature. Is there a workaround ?