Page History
| Widget Connector | ||
|---|---|---|
|
This page describes the migration path you can follow to migrate Xray data from Jira Server/Data Center to Jira Cloud. If you have any questions about which approach best suits your organization, please contact our support team directly.
...
| Note | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Before migrating from Xray Server/DC to Cloud be sure you've completed the steps recommended at "Steps to a successful migration":
Ready for a Checklist? Make Sure you do not forget any step and download our Xray Migration from Server to Cloud Checklist.
Learn more at "Steps to a successful migration". Also make sure you are aware of the differences between Xray Server and Xray Cloud. Be also sure, that if you select the Xray Cloud Standard you are aware of the storage limit. If the storage offered by Xray Standard is not enough, you might consider upgrading to Xray Enterprise. |
Server/DC vs Cloud - Product Comparison
...
For a full comparison between the Server/DC and Cloud versions of Xray, please refer to Xray Server and Xray Cloud.
Jira Cloud Migration Assistant
...
Before the Xray migration stage is executed, all issues and Jira entities are migrated by Atlassian's JCMA. In order to guarantee that Xray migration is successful, all these Jira entities must be 100% migrated, without warnings. If you encounter problems in Jira's migration stage, please contact the Atlassian support team.
Edit Issue Type Names
The name of the issue types needs to be the same on both server and cloud before starting the migration.
The Issue Type Precondition/Pre-Condition may have to be changed as it is named differently in the server and cloud versions of Xray.
https://support.atlassian.com/jira-cloud-administration/docs/add-edit-and-delete-an-issue-type/
| Note | ||||
|---|---|---|---|---|
Due to the way the "Migrate all data at once" option works on JCMA, when choosing this option a few additional steps must be taken to ensure compatibility with the Xray migration. So if you are using the "Migrate all data at once" option, please follow the steps below: - On the Server side, rename all Xray issue types like this (avoid spaces before and after):
- Still on the Server side, and only after the Xray types are renamed, create 6 dummy issue types like the list below:
After carrying out the previous operations, the issue types on the Server should look like this:
After the migration is completed, the dummy issue types created with this purpose can be deleted, and the Xray issue types can be renamed back to their original names.
|
Edit Requirement ↔ Test Link
...
The Issue Security Scheme may restrict Xray's access to issues during the migration.
If you are using Security Levels for Xray Issues - e.g. ( Test, Test Set, Test Plan, Test Execution, Sub-Test Execution and Pre-Condition) - you'll have to temporarily add "Any Logged in user" to all the security levels used by Xray Issue Types or remove all the Security Schemes/Levels from those issues.
Preflight Checks
These checks are meant to help you plan your migration by taking into consideration Xray related constraints. The checks will let you know if:
- the migrated Projects have the required permissions.the group of Projects that you are migrating contain contains any Xray links to data outside of these Projects.
...
The preflight checks are available when the Jira Cloud Migration Assistant is installed and a version of Xray supporting the migration to Cloud is also installed. The page can be found in the Administration → Manage Apps → Xray → Cloud Migration. Here you should add see a table with all the instance projects listed, select all the projects for your migration and then press Validate. If there are no errors, you can leave this page and proceed with your migration through the Jira Migration Assistant. If there are any errors you can see the details and steps to fix the issues.
Example: Project Xray Test Project XT was selected for migration. The preflight checks found that there is a link to another project which that is not part of the migration (XDTPXray Dev Test).
We'll add select the missing project to projects for the preflight checks and validate.
There are no more errors, meaning that these two the projects can be migrated together safely. We can now go back to the Jira Migration Assistant and plan our migration with both projects.
...
| title | Temporary Feature |
|---|
...
.
Migrate all users
It is recommended that you select the option "All users and groups from the Jira directory" when choosing which users to migrate in the Jira Migration Assistant. This is due to the way that Jira checks which users are related to a project which will not consider users assigned to Test Runs.
...