Jira cloud-to-cloud migration with Xray data

Our client approached us when they were in a complicated situation. They were accessing the Jira system of another company, where they were working on many projects; however, the system was to be shut down soon. There was important data that the client wanted to retain, and therefore they needed to perform a cloud-to-cloud migration to their own Jira system. The client had only partially succeeded in this - the data from the Xray application was missing.

As the first step, we conducted an analysis of both the source and target environments. It was primarily necessary to map out everything that was present and whether the migrated items conflicted with the target data (applications, projects, automations, custom fields...).

As the next step, we established a testing environment so that we could test the migration without affecting the target environment, and we agreed on the scope of the migrated data - it involved about three dozen Jira projects, with roughly half of them using the Xray application. The data copy itself, performed through the Atlassian tool, was not complicated, but after the migration, the Xray application data was missing, which we had already anticipated.

We contacted the Xray application vendor and, based on the documentation received, we found that the migration needed to be divided into two larger steps:

  1. Migrate tests, test sets, and conditions (not issues themselves, but the Xray data added to these issues)
    Export the data of these elements using the Xray Document Generator and import them into the target environment via the Xray Test Case Importer.

  2. Migrate test runs data
    Get the data via the GraphQL API and upload them to the target environment via the REST API using a script we created

Furthermore, it was necessary to merge Xray configuration (e.g. test statuses and test steps statuses) and manually configure the migrated projects (e.g. add Xray custom fields).

After completing the test migration, we agreed with the client on post-migration adjustments in the target environment. For example, we set the permission schemes so that the migrated projects were read-only.

After approving the results of the test migration, when the client received full access to the test environment and could test everything, we proceeded to the production migration.

Thanks to the migration plan that was created based on the test migration, we were able to complete the production migration without major complications.

1 comment

Comment

Log in or Sign up to comment
Kishan Sharma
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 24, 2024

Thank you for sharing @Hana Kučerová 👍

Like Hana Kučerová likes this
TAGS
AUG Leaders

Atlassian Community Events