Dependent Dropdowns in CSV Imports

[Joshua Smith]

Hi all,

I'm in a team-managed Jira Software project and need to import hundreds of issues via CSV. Some of the fields required for import are dependent dropdowns, but they are not importing properly.

The closest I've gotten is that it will import the parent dropdown choice only. So for example, if I was filling the issue out manually and the field is, "What's the weather like today?" The initial dropdown might have options "it's nice out" and "it isn't nice out". Then if I select "it's not nice out", a second dropdown would appear with options "it's too hot", "it's too humid", or "the air quality is bad"

I tried exporting and following the same format as the export, which is "it's not nice out -> it's too hot". It didn't import at all without the "->" but when I formatted it like the above export format, it does upload - but without the secondary choice, so if I view the issue it has "it isn't nice out" but the secondary dropdown is blank.

I haven't been able to find anything about this at all - has anyone worked with dependent dropdowns in CSV imports before? Thank you!

[Vikrant Yadav]

Hi @Joshua Smith  I tried same it's working fine. Separator is fine. 

USA -> New York

Try one thing, tried to export one existing issue into csv ( with dependent field column) having value in this field. In export, you will find the how values are separated in this field, You will use that same separator while importing issues via csv.

Issue Type	Issue key	Issue id	Summary	Custom field (Countries > States)
Story	GOOG-15	10009	Test Case	USA -> New York

[Sam-Kai Huang]

Hi @Vikrant Yadav I am still encountering the same problem when importing issues with dependent dropdowns. Despite following the recommended format (Parent -> Child), the secondary dropdown remains empty.

[Vikrant Yadav]

I have to tried on my machine, it works fine. 

This works well in Jira cloud!
You need to export the field first to see how delimiter is the correct for your site (->, =>, >).

Here the delimiter is "->" and i was able to update a cascade field 

[Sam-Kai Huang]

Hey @Vikrant Yadav Thanks for the guidance! The delimiter is "->" in the exported file and i was able to import the recodes with the same fields. However, the child value (such as No PII Data) is missing after the import.

export: 

import: 

[Vikrant Yadav]

Hi @Sam-Kai Huang  It's weird because on my machine it's working fine. 
I suggest you to check with Atlassian Support, why it's not working for you.