Users unable to set Parent-Child cascading select values on CSV import

[Edgar Oregel]

We've received reports of users importing a CSV with Jira tickets containing values for cascading select values, both parent and child values, and the child values not being set on import. When the CSV is imported, only the Parent values are set, and the Child values are not. 

I am a Jira admin on our Jira Software (server), and i've used the External System Import feature with the same CSV. When i import using that feature, the child values get set, but if i as a Jira admin use the user feature, i.e. Issue nav --> Import from CSV, the child values don't get set. 

Is this a limitation of Jira? I've found a ticket submitted back in 2013 to the Atlassian team that is still "Gathering Interest", so i'm assuming it's by design, but has anyone found any workarounds or solutions to this?

https://jira.atlassian.com/browse/JRASERVER-34202

I also found documentation saying that to do this, you must use the External System Import but nothing really directly saying "Users are not allowed to do this" restriction. 

https://community.atlassian.com/t5/Jira-questions/Importing-data-to-a-cascading-selection-field/qaq-p/181942

We, as Jira Admins, don't want to become part of Customer's workflows or have them become dependent on us using the External System CSV Import.