Page History
...
Jira-managed data: Includes issue summaries, descriptions, custom fields, workflows, and permissions. This data is transferred using Atlassian’s Cloud-to-Cloud migration tool.
X-rayXray-managed data: Includes test steps, test runs, links between issues (e.g., Test → Test Plan), and X-ray-specific metadata. These need to be migrated separately.
...
- The CSV source file must follow some simple rules. Preparing the source file. You can name the fields as you wish since they are going to be mapped during the importation process, but three mandatory fields must be mapped.
- Issue Id – a unique identifier for the issue; this field is used to group lines that belong to the same test case or to identify a precondition or a test set.
- Summary – this field is mandatory since Jira doesn’t allow you to create an issue without a summary.
- Test Type – this field defines the test type of the each test to import. The test type must match one of the types of the project to which the test is being imported.
Finally, the remaining Relations and the Test Run's Data should be transferred by performing exports and imports with REST API and Xray's GraphQL API. This method is necessary because this data is not saved in Custom Fields but by our field entities, which cannot be handled by default export methods or the REST API cannot handle.
Final Step: Before importing the Xray Data: Re-index the Project
...
After re-indexing, you can import the Xray data to the destination instance.
...