-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
8.13.0, 8.20.0, 9.4.0, 9.12.0, 9.12.12
-
8.13
-
3
-
Severity 3 - Minor
-
1
-
Issue Summary
Project import validation fails with NullPointerException referencing CustomFieldValue.xml.
This happens because of NullPointerException is due to the missing stringvalue/textvalue/numbervalue/datevalue associated to the custom field entries defined in the entities.xml file.
This error should not happen in the first place and this bug is to address this issue.
Steps to Reproduce
- Generate an XML backup from your source Jira instance
- Run a Project Import on the destination instance
- Run into the problem
Expected Results
Project import runs successfully.
Actual Results
Project import does not finish successfully.
The below exception is thrown in the atlassian-jira.log file:
2021-06-07 13:07:55,949+0000 JiraTaskExecutionThread-6 ERROR Test 787x492x1 7zbvjj 172.29.186.150 /secure/admin/ProjectImportSelectProject.jspa [c.a.j.imports.project.DefaultProjectImportService] There was an unexpected problem processing the file '/xxx/xxx/CustomFieldValue.xml' when performing a project import.
java.lang.NullPointerException
at com.atlassian.jira.imports.project.customfield.TextLengthValidatingCustomFieldImporter.canMapImportValue(TextLengthValidatingCustomFieldImporter.java:24)
at com.atlassian.jira.imports.project.handler.CustomFieldValueValidatorHandler.validateCustomFieldValueWithField(CustomFieldValueValidatorHandler.java:98)
at com.atlassian.jira.imports.project.handler.CustomFieldValueValidatorHandler.handleEntity(CustomFieldValueValidatorHandler.java:73)
The cause of incorrect data in the XML source files is unknown.
Workaround
Follow the Solution step from the knowledge article
