Versions Compared

Old Version 55

changes.mady.by.user Sofia Canario

Saved on

compared with

New Version 56

changes.mady.by.user Victor Tisbierek

Saved on

Key

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

...

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:

  • Pre-Condition → Xray Precondition
  • Test → Xray Test
  • Test Execution → Xray Test Execution
  • Test Plan → Xray Test Plan
  • Test Set → Xray Test Set
  • Sub Test Execution → Xray Sub Test Execution

- Still on the Server side, and only after the Xray types are renamed, create 6 dummy issue types like the list below:

  • Precondition
  • Test
  • Test Execution
  • Test Plan
  • Test Set
  • Sub Test Execution

After carrying out the previous operations, the issue types on the Server should look like this:

Image Added

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.

Warning

Sometimes when migrating with the "Migrate all data at once" option, the issue type avatars can be broken on the Cloud side after the migration (i.e., the migration is successful but the icons of the issue types are missing). If that happens, the icons can be downloaded and updated manually on the Cloud following the procedure described here.

Warning

This procedure is only applicable when using the option "Migrate all data at once" from JCMA. If the migration is carried out using the "Choose what to migrate" option (i.e., choosing the specific projects to migrate), the extra steps described above can be disregarded.


...