[All Adaptavist Apps]
You may find some issues during the migration. Here, you will find tips for dealing with them.
First of all, take into account that the full migration process includes a step where the source configuration is imported to the target instance. Our pages about typical issues found when exporting or importing configurations may, therefore, be useful when you are migrating complete projects.
The following sections reference some common problems which may specifically affect data import.
Sometimes a data import will fail with a message similar to the following:
The custom field 'XXXX' in the backup project is used by issue types 'AAAA, BBBB' but the field with the same name in the current JIRA instance is not available to those issue types in this project.
This error occurs even though the custom field is actually applicable for those issue types at the target instance. This is a result of the bug, JRASERVER-28006. The workaround for this issue is to make the custom field available for all issue types by completing the following steps:
config.xmlfile from the ZIP file you are importing, and then importing that configuration file into the target. In this case, do not use the Skip import of custom fields option described in Step 2.
Sometimes you might find a validation error without any specific information, similar to the following:
WARN 11:00:56,968 The attachment 'MMMMMMMMM.zip' does not exist at '/tmp/com.awnaba.projectconfigurator1493567880435/data/attachments/XXXXXXXXXXX'. It will not be imported. WARN 11:00:56,968 The attachment 'screenshot-1.png' does not exist at '/tmp/com.awnaba.projectconfigurator1493567880435/data/attachments/YYYYYYYYYYYY'. It will not be imported. WARN 11:00:56,968 The attachment 'screenshot-1.png' does not exist at '/tmp/com.awnaba.projectconfigurator1493567880435/data/attachments/ZZZZZZZZZZZZZ'. It will not be imported. INFO 11:00:56,969 Project Import: Validation errors were found. The import cannot continue.
The Jira log file may also not provide any additional detail for the issue. In our experience, this problem is usually caused by a value for a text field that exceeds the limit for maximum text field size at the target instance. See point 3 in the section named "Matching properties of both instances" in Atlassian's Preparing for migrating projects.
You may encounter a warning in the data import trace similar to the following:
WARNINGS: Unable to import custom field 'Time in Status'. The custom field type does not support project imports.
This message is a warning; it will not stop the import. It simply means that the values for that custom field will not be imported because the custom field type does not support data imports, as it does not satisfy the requirements defined in Atlassian's How to make a custom field "importable" for project imports page.
However, to the best of our knowledge, this is not relevant in practical terms. That field belongs to Jira Charting App and its values are calculated automatically from the story of issues included in graphics. If these values are not imported, they will be recalculated again as needed.
The exported data will contain date/time fields but no reference to the timezone where those values are valid. As a result, if the source and target instances use different timezones, the time values will be shifted by the time difference between those zones. See the following bug reports:
The workaround is to ensure that the source and target instances are using the same timezone.
With this error, the data import fails with this message which explains that a number inside square brackets is not a valid string representing a number.
Usually, this is a consequence of bug JRASERVER-59681. This bug ticket by Atlassian explains how the import can be fixed.
This error occurs when importing Sprint data, as shown at the top of the error trace:
Data import failed with exception: null java.lang.NumberFormatException: null at java.lang.Long.parseLong(Long.java:552) at java.lang.Long.valueOf(Long.java:803) at com.atlassian.greenhopper.imports.SprintImportHandler.endTable(SprintImportHandler.java:105) at com.atlassian.jira.imports.project.ao.handler.ChainedAoSaxHandler.endTable(ChainedAoSaxHandler.java:263) at com.atlassian.jira.imports.project.ao.handler.ChainedAoSaxHandler.endElement(ChainedAoSaxHandler.java:190) at com.atlassian.jira.imports.project.ao.handler.ChainedAoSaxHandler.endElement(ChainedAoSaxHandler.java:151)
The Jira knowledge base article, Project Import fails with Unexpected import failure, describes this issue, points to the bug ticket with the root cause, and recommends a solution.
Starting with Jira 7, sprint and ranking data is migrated with the rest of the project data. This works well with Project Configurator’s feature that migrates Scrum or Kanban boards as part of the project configuration, providing a complete solution for the migration of Jira Software projects.
However, problems can occur when there are sprints including issues for more than one project. In this case, these sprints will be duplicated—one sprint will be created for each project involved—and the ranks will only maintain the relative order among issues belonging to the same project. This is a result of the underlying data transport technology that imports one project at a time. Project Configurator calls this process once for every project to be imported.
This problem is described in Project Import fails due to too many errors. This article also explains a workaround to fix the exported data. Bear in mind that this fix is quite complex and is defined for an XML backup. Remember that if you have exported with Project Configurator, the
data.zip file will be located under the
data folder in the exported ZIP. After changing it, the edited version must be compressed back into the same location in the exported ZIP.