Versions Compared

Key

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

...

E.g., all the Tests in the Test Plans of Project A must be part of the migrated Projects.

Warning

Avoid data change during the migration, otherwise the migration might fail.

Understand and Communicate the Limitations

Issue History and Test Run Activity

creating, modifying, or deleting Issues related to Xray or connected projects during migration, as this can cause failures if more than 100 Issues are missing. Disable all automation and third-party app modifications to prevent exceeding this limit. Ensure all Jira projects are fully migrated; otherwise, Xray won’t find the expected Issues. Also, remove issue security schemes or set them to "Any logged-in user" before migration to avoid permission-related failures.

Understand and Communicate the Limitations

Issue History and Test Run Activity

Due to the Due to the textual nature of the data in the activity logs, the entries are mostly copied directly. The language, phrases and markups may differ from server to cloud.

...

All the linked data must be migrated together so data integrity can be guaranteed on the cloud.

Automated Step Library

Not supported by Xray Cloud and will not be migrated.

Automated Steps Library will be migrated but you need to perform a re-index. Check more details on [Xray] Will the automated Automated Step Library be migrated to the Cloud when performing a migration from Server/DC to the Cloud using JCMA?

Cucumber settings

Will not be migrated to cloud. (Miscellaneous settings section)

...

In the past we've seen migrations failing due to archived projects. Xray does not have visibility/permissions into these projects so please check if you are trying to migrate archived projects.

Project Level Settings

The project level settings get transferred when migrating from Xray Data Center to Xray Cloud (except for Default Column Layouts settings).

Info

If you want to migrate archived projects,

Info

If you want to migrate archived projects, you first need to unarchived them. 

Follow this article to understand how to check which projects are archived: [Xray] How to get all Archived Projects?

...

There are no more errors, meaning that the projects can be migrated together safely. We can now go back to the Jira Migration Assistant and plan our migration with both projects.

...

Preloading Xray Data Before Migration

Atlassian provides a feature

...

 that allows you to migrate Jira attachments in advance, saving you time on the migration day.

...

It

...

is essential to

...

have Xray version 7.8.2

...

or the latest installed, as this version includes the attachments feature. Additionally, you'll need to ensure

...

that JCMA (Jira Cloud Migration Assistant) is updated to version 1.

...

12.

...

16 or higher. Below is a step-by-step guide

...

on how the preload process works:

1. Install Xray version 7.8.2

...

or the latest

This version is

...

required as it introduces the attachments functionality.

...

2. Ensure JCMA version 1.

...

12.

...

16 or above is installed

...

com.atlassian.jira.migration.app.data.preload.feature

...

Starting from JCMA 1.12.16, no feature flags are required. A new option, "Preloadable app data only," is now available on the projects screen.

  • If this option does not appear, customers can contact Atlassian to enable the feature flag for them.
  • For JCMA versions 1.12.13 to 1.12.15, customers must reach out to Atlassian to have the feature flag enabled manually.

3. Additional References

For more details on preloading app data before migration, refer to Atlassian's official documentation

...

.

By following these steps, the preload process should work as expected, ensuring a smoother migration with minimal downtime.

Info

Go here to see more about Xray attachments.

...