Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This tool has some limitations though; it cannot transfer apps/add-ons related data between instances unless apps are prepared for it.

Fortunately, Xray is now ( since v3.2) 3, Xray is able of taking advantage of this mechanism; on previous versions, issues would be restored but the testing data wouldn't.

...

Requirements and Limitations

NotesAdditional information

Your backup file must have been created using Jira's backup tool. You cannot import a project from a backup using your native database tools.


The version of Jira in which the backup was created must be identical to the target Jira instance.

It is recommended to have also the same version of the apps on the target JIRA instance.

Jira versions do not match.

If the instance of Jira had any app/add-on having their own custom field installed when the backup file was created, and the custom field was used in your project, then your target instance of Jira must have the same version of the app installed for the Project Import tool to automatically work.

Custom fields plugin versions do not match.

The Project Import tool will lock out your instance of Jira during the actual data import (not during the validations).  Ensure that your instance does not need to be accessible during this time.


You cannot import a project directly from Jira Cloud to Jira Server. The importer will display errors about version mismatches. 

More information on migrating information from Xray Cloud to Xray server soon.

How to backup a project

Jira does not provide a project level backup utility; instead, it provides a global backup utility available in System > Import & Export > Backup System.

...