Page History
...
- Zephyr >= 4.0.0
- Zephyr and Xray should be both installed
- project where migration is being done must have Xray issue types (at least the Tests, Test Executions and Test Plans)
- you may use the "Add Xray Issue Types" action shortcut available in the project settings page
- requirement issue types used in Zephyr must be configured in Xray
- all the different issue types that Zephyr Tests cover should be configured in Xray's Issue Type Mapping settings.
- defects issue defect issue types used in Zephyr Zephyr must be configured in Xray
- all the different issue types are being used as defects in Zephyr should be configured in Xray's Issue Type Mapping settings.
- create similar Test Statuses and Test Step Statuses in Xray; this is not mandatory but may ease the process, which will always ask you to make the mapping between Zephyr statuses and Xray counterparts
- make sure Zephyr is using different issue links between Test<=>Defect and Test<=>Requirement, by going into Zephyr's configuration settings
- Do not change, create or delete any issue in the Project while the importation is running
- We strongly recommend you to make a Backup backup of your Jira instance before doing the importation.
...
| Info | ||
|---|---|---|
| ||
The current process performs an inline migration, i.e. Tests and data is migrated to Xray and the original entities are "lost". Thus, we recommend to backup your JIRA Jira instance before performing the migration. Also, as the amount of data to migrate may be considerable large, we advise you to perform this on non-working hours. Please also make sure that users are not changing data on the project while the migration is being done. |
...
Most information will be migrated seamless seamlessly but please check the following table in more detail.
...
| Supported Features | Unsupported |
|---|---|
Inline migration (not cloning) of:
(*) Cycle folders will be migrated to Test Executions, since the semantics on Xray are a bit different in terms of entities/organization. |
|
| (*) Cycle folders will be migrated to Test Executions, since the semantics on Xray are a bit different in terms of entities/organization. | |
How it works
Within this section you're able to find the exact mapping of entities from Zephyr to Xray.
Mapping of information
| Zephyr entity | Xray entity | Notes |
|---|---|---|
Test
| Test
|
|
| Cycle | Test Plan (optional)
Test Execution, linked to the previous Test Plan
| The Test Execution created here will contain the Executions assigned directly to the Cycle, since in Zephyr you can have Executions at that level besides on each folder. Please note that...
|
| Cycle's folder | Test Execution, linked to the Test Plan created earlier from the Cycle
| |
| Ad-hoc Cycle | Test Plan (optional)
Test Execution, linked to the previous Test Plan
| |
Execution
| Test Run
|
| Info | ||
|---|---|---|
| ||
All issues will be created in the project where the migration is being performed. |
How to use
Migrating data Performing the migration is easy; however, it is currently limited to Jira administrators.
...
Suppose you have a project that you wish to migrate from Zephyr for Jira to Xray and that the requirements mentioned above are met.
To start the importation process:
- Log in with an administrator account;
- Go to System>Import and Export>External System > Import and Export > External System Import;
- Select Xray's Zephyr Importer.
Then, you need to ....
Upon successful connection, you can optionally define a label to assign to the Test issues that will be created. This may be quite useful if you need a quick way to identify the newly created issues. The label syntax is restricted in the same way as the label fields in Jira. We recommend using a unique label with numbers.
...