Import Issues from CSV with a required Cascading Select field

[Michelle Gronwold]

We have just updated our Jira Data Center server to v10. I have a user that uses the "Import Issues from CSV" regularly. Since the upgrade she is now unable to import her CSV files. The error is "Issue can't be created due to the error/s [ Module is required. ]"

The Module field is a cascading select field. It is set as a required field. The import has worked in the past.

In testing I found that if I set the Module field as optional the import will work fine. If I set other fields as required, fields that are not a cascading select field, the import also works fine.

Is there an issue with the "Import Issues from CSV" function if there is a required cascading select field in v10 Data Center?

[Michelle Gronwold · Accepted solution]

I found a work around solution:

1. Set the cascading select field as optional in the Field Configuration.
2. Add a validator to the workflow on the Create Issue Transition to make the cascading select field required.

If the requirement is in the workflow, and not the field configuration, you can create the jira issues with only filling data in the parent/1st dropdown, leaving the child/2nd dropdown empty.

[Michelle Gronwold]

It looks like that with the upgraded version of Jira Data Center, when you set a cascading select field to required you now need to select something in both dropdown selections. In previous versions, you could always leave the 2nd dropdown blank.

Any tips on how to format a cascading select field in CSV file? I have tried "field1 -> field2", "field1 => field2" and neither are working.