I am attempting to import issues using a csv file. In the file I have Bugs, Stories, and subtasks.
The bugs and stories import correctly, the subtasks are throwing an error. I have both the Issue ID and the Parent ID on the csv file.
The import file looks like this:
IssueID Issue Type Parent Issue ID
US2482 Story
DE722 Bug
(blank) Subtask US2482
The configuration file has this:
"field.Issue ID" : "issue-id",
"field.Parent issue ID" : "subtask-parent-id",
Is appears the subtask is importing, but fails (null point exception) on creating the link to the Story
2013-11-25 18:46:14,253 INFO - Only new items will be imported 2013-11-25 18:46:14,254 INFO - Importing issue: ExternalIssue{externalId=US2482, summary=OUT OF SCOPE - View of Outstanding Cases (Future State), issueType=7} 2013-11-25 18:46:14,442 WARN - Custom field 'Story Points' has multiple configuration schemes. Importer is unable to extend custom field context automatically. 2013-11-25 18:46:14,489 INFO - Importing issue: ExternalIssue{externalId=DE722, summary=US2457 - Contact - Error on warning logic for New Contact entry, issueType=1} 2013-11-25 18:46:14,624 INFO - Importing issue: ExternalIssue{externalId=autoid-332276842025079510, summary=SFDC Configuration, issueType=5} 2013-11-25 18:46:14,761 INFO - Importing issue: ExternalIssue{externalId=DE716, summary=US 2457 - CONTACT - First Name is not Required Field, issueType=33} 2013-11-25 18:46:14,908 INFO - ------------------------------ 2013-11-25 18:46:14,908 INFO - Finished Importing : Issues 2013-11-25 18:46:14,908 INFO - ------------------------------ 2013-11-25 18:46:14,908 ERROR - Unexpected failure occurred. Importer will stop immediately. Data maybe in an unstable state java.lang.NullPointerException at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.addOptions(DefaultJiraDataImporter.java:1559) at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.importExternalCustomFields(DefaultJiraDataImporter.java:1199) at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.createIssue(DefaultJiraDataImporter.java:954) at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.importIssues(DefaultJiraDataImporter.java:837) at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.doImport(DefaultJiraDataImporter.java:422) at com.atlassian.jira.plugins.importer.imports.importer.impl.ImporterCallable.call(ImporterCallable.java:26) at com.atlassian.jira.plugins.importer.imports.importer.impl.ImporterCallable.call(ImporterCallable.java:15) at com.atlassian.jira.task.TaskManagerImpl$TaskCallableDecorator.call(TaskManagerImpl.java:374) 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:250) at java.lang.Thread.run(Thread.java:722)
How do I resolve linking issue for parent/child?
Resolved locally. csv file cantained a poorly formated field.
Hi Jeanne,
Please send me the csv file. And check weather any mandatory field is there in your issue screens.
thanks,
Patina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
It's currently not supported by JIRA Importers Plugin. There is an improvement request for it at https://studio.atlassian.com/browse/JIM-622
Your comment and/or vote there would definitely help prioritize it accordingly.
Thanks,
Patina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Patina,
The issue you reference talks about importing subtask to existing issues in JIRA. I am trying to import both the story and the subtask at the same time.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.