Error Importing CSV File - issueId should not be null
Symptoms
Importing issues from a CSV file fails and the following is displayed:
The error below appears in the import's detailed log:
2013-12-03 17:48:42,897 INFO - ------------------------------
2013-12-03 17:48:42,897 INFO - Finished Importing : Issues
2013-12-03 17:48:42,897 INFO - ------------------------------
2013-12-03 17:48:42,897 ERROR - Unexpected failure occurred. Importer will stop immediately. Data maybe in an unstable state
com.atlassian.jira.util.dbc.Assertions$NullArgumentException: issueId should not be null!
at com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:29)
at com.atlassian.jira.issue.label.DefaultLabelManager.getLabels(DefaultLabelManager.java:91)
at com.atlassian.jira.issue.customfields.impl.LabelsCFType.getValueFromIssue(LabelsCFType.java:132)
Diagnosis
The Field Configuration associated with the Project and Issue Type(s) configured during the CSV import contain Required fields besides Issue Type and Summary.
Cause
This happens because the JIRA Importers Plugin tries to validate if the issues are valid for importing, and when the validation fails the error above is thrown. This is being tracked on Unable to locate Jira server for this macro. It may be due to Application Link configuration. .
Workaround
- Make all fields Optional (Summary and Issue Types will always be required) - see Specifying Field Behavior - Making a field required or optional;
- Import the CSV file;
- Set the necessary fields as Required again.
Last modified on Feb 19, 2016
Powered by Confluence and Scroll Viewport.