-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
14
-
17
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Currently the CSV import feature does not support Multi-Level Cascading Select fields (that are provided via the Multi-Level Cascading Select plugin).
This can be inconvenient for some users who would like to use this field during CSV imports. Hence, it would be useful if the CSV import supports the usage of the Multi-Level Cascading Select field.
- duplicates
-
JRASERVER-5775 Unable to import into Cascading Select fields
-
- Closed
-
- relates to
-
- Gathering Interest
- mentioned in
-
![[Atlassian Documentation] Page](/images/icons/generic_link_16.png "[Atlassian Documentation] Page")
Page
No Confluence page found with the given URL.
-
Page
No Confluence page found with the given URL.
-
Page
No Confluence page found with the given URL.
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
[JRASERVER-34202] Allow CSV import to support Multi-Level Cascading Select plugin fields
Hey Lee, I have come across this issue myself in the past.
I see there is an app on the market place, why don't you give the trial a try and see how it goes from there?
Are you considering moving to cloud by any chance? I'm considering making an app for fun, and this may be a good first project.
8 years gathering interest. Sounds about right. We get a comment once every six months on this one so it's my turn to poke the embers.
This is still an issue and is causing a lot of wasted effort on my team. I'd ask for an update from Atlassian but, yeah ... I know, communicating with their customers isn't their strong point.
This feels like a pretty important bug to fix. Atlassian you should include in the custom fields documentation that this cannot be imported.
even a CSV import of a standard select list (non-cascading) would be great! This can't be done yet.
We have about 300+ fields in the child list that aren't getting mapped, so you can understand how manual that can be.
Would love an update on this please.
exactly as Sune mentioned; "Select List (cascading)" are supported ootb
@Joshua Wyss: I think this issue is actually for the plugin - I did manage to import values into a Cascading Select List using the 'Parent Value -> Child Value' format described in the documentation.
Because it isn't possible to do importing multi-level cascading select fields via CSV, we are considering flattening our issue (ie. getting rid of the cascading selects). It would be a very useful feature to us.
@Amir Katz. this suggestion is for the Cascading Select List that is built into Jira by Atlassian not for the plugin.
I am a bit confused here - this feature (Multi-Level Cascading Select) is in a Marketplace plugin. According to its marketplace page, it already has a CSV import feature (link ):
Multi-Level Cascading Select is a new custom field type supporting any number of levels.
It provides easy configuration, a powerful searcher, a CSV importer and intuitive reports making it perfect for any organisation.
So I don't understand why people ask Atlassian to add support for it.
I have data on issues that consists of fields representing start and end dates as a fiscal year and quarter using 2 cascading select fields. I have a potential initial data import of approx 10K issues with these fields. Lack of this functionality will require going back and setting them by hand after the initial data load or perhaps via the REST API, assuming that functionality is in place, haven't tried that yet. Basically, any field delivered by the base system should be able to be imported in this manner. Lack of this consistency in behavior causes major unexpected administrative issues.
Rediculous that you can use the import to update multi-level but not create, this can't be a massive change to the coding - where it takes forever to update these things manually...
Vinay Shekar
added a comment - + 1 
Jason Jennings
added a comment - It would be valuable for JIM JSON importer to support the MLCS field too.
Jason Jennings
added a comment - It would be valuable for JIM JSON importer to support the MLCS field too. ++ 1
I have tested this with latest JIM version and it is working fine with system admin external CSV import but not working for non-admin CSV import. and throwing following error:
2014-11-07 07:40:32,855 WARN - Cannot add custom field value: null
java.lang.NullPointerException
at com.atlassian.jira.plugins.importer.imports.importer.impl.customfields.CFValueHandlerMultiple.handleOptionsHierarchy(CFValueHandlerMultiple.java:76)
at com.atlassian.jira.plugins.importer.imports.importer.impl.customfields.CFValueHandlerMultiple.prepareCustomFieldValue(CFValueHandlerMultiple.java:40)
at com.atlassian.jira.plugins.importer.imports.importer.impl.customfields.CustomFieldValueFactory.prepareRawValueForCustomField(CustomFieldValueFactory.java:63)
at com.atlassian.jira.plugins.importer.imports.bulkcreate.BulkCreateCustomFieldsHelper.prepareValueForCustomFields(BulkCreateCustomFieldsHelper.java:47)
at com.atlassian.jira.plugins.importer.imports.bulkcreate.BulkCreateDataImporter.handleCustomFields(BulkCreateDataImporter.java:353)
at com.atlassian.jira.plugins.importer.imports.bulkcreate.BulkCreateDataImporter.externalIssueToInputParams(BulkCreateDataImporter.java:312)
at com.atlassian.jira.plugins.importer.imports.bulkcreate.BulkCreateDataImporter.runImporterEngine(BulkCreateDataImporter.java:150)
at com.atlassian.jira.plugins.importer.imports.bulkcreate.BulkCreateDataImporter.doValidate(BulkCreateDataImporter.java:110)
at com.atlassian.jira.plugins.importer.imports.bulkcreate.ValidationCallable.call(ValidationCallable.java:27)
at com.atlassian.jira.plugins.importer.imports.bulkcreate.ValidationCallable.call(ValidationCallable.java:12)
at com.atlassian.jira.task.TaskManagerImpl$TaskCallableDecorator.call(TaskManagerImpl.java:527)
at com.atlassian.jira.task.TaskManagerImpl$TaskCallableDecorator.call(TaskManagerImpl.java:490)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at com.atlassian.jira.task.ForkedThreadExecutor$ForkedRunnableDecorator.run(ForkedThreadExecutor.java:253)
at java.lang.Thread.run(Thread.java:724)
2014-11-07 07:40:32,856 WARN - The value [ {null=FIAT, 1=500} ] can't be added to the Custom Field [ Brand/Nameplate ]. The value [ {null=FIAT, 1=500} ] can't be found or is in the incorrect format
I also agree. Further, the documentation for CSV import as of yesterday at least gave the exact syntax on how to import a cascading select field.
LL
added a comment - ^I agree with Mark. There should be an advisory note. 
Mark Jelic
added a comment - Seems a roundabout way to get to the final ticket that is still open and Voteable... And with only 4 votes currently, and yet previous tickets have had 30+ votes... Obviously you have lost some followers along the way!
If Cascading Select fields are that problematic, at a minimum you should put an advisory note on the description of that field type when you are considering adding that to your project, along the lines of "Please note that there is no CSV import facility for this sort of field"... At least then I know not to use it!
Mark Jelic
added a comment - Seems a roundabout way to get to the final ticket that is still open and Voteable... And with only 4 votes currently, and yet previous tickets have had 30+ votes... Obviously you have lost some followers along the way!
If Cascading Select fields are that problematic, at a minimum you should put an advisory note on the description of that field type when you are considering adding that to your project, along the lines of "Please note that there is no CSV import facility for this sort of field"... At least then I know not to use it!
Thanks for the response, Jarrod. I'm currently on JaaS and have no plans to move or use a plugin for functionality that works in one section of Jira and not another.