Page History

Versions Compared

Key

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

...

As of Xray v3.3, the importer only performs inline migration of data (i.e. Zephyr's Test issues are "moved" to Xray's Test issues).

Before using the Zephry Import tool

Before using the tool, please check the necessary requirements and also the existing features and its limitations.

Requirements before proceeding

Zephyr >= 4.0.0
Zephyr and Xray should be both installed
project where migration is being done must have Xray issue types
- you may use the "Add Xray Issue Types" action shortcut available in the project settings page
requirement issue types must be configured in Xray
- all the different issue types that Zephyr Tests cover 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

Info

title	Please note

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 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.

Features and Limitations

Below, please find a list of the support features and current limitations.

Most information will be migrated seamless but please check the following table for the current possibilitiesin more detail.

Supported Features	Unsupported
Inline migration (not cloning) of: Test , and Test steps Test and Test step attachments Links between Tests and Defects/Requirements Cycle including Cycle folders* Executions defects (global and step level) attachments (global and step level) result (global and step level) comments (global and step level) assignee (*) Cycle folders will be migrated to Test Executions, since the semantics on Xray are a bit different in terms of entities/organization.	All Zephyr executions from the Ad-hoc cycle; only the last Execution is migrated Custom fields in Test steps and on the Execution Activity information Test Statuses and Test Step Statuses Cycle folders as such*

Supported Features

Unsupported

Inline migration (not cloning) of:

Test , and Test steps
Test and Test step attachments
Links between Tests and Defects/Requirements
Cycle
- including Cycle folders*
Executions
- defects (global and step level)
- attachments (global and step level)
- result (global and step level)
- comments (global and step level)
- assignee

(*) Cycle folders will be migrated to Test Executions, since the semantics on Xray are a bit different in terms of entities/organization.

All Zephyr executions from the Ad-hoc cycle; only the last Execution is migrated
Custom fields in Test steps and on the Execution
Activity information
Test Statuses and Test Step Statuses
Cycle folders as such*

Initial requirements

...

you may use the "Add Xray Issue Types" action available in the project settings page

How it works

...

Notas

quando a coluna do Step está vazia <undefined>no rollback; migration is inline
all issues will be created within the same project where the migration is being done

...

Content

Space Tools