Xray v3.3 provides a built-in importer for Zephyr for Jira.

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

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 in 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*

How it works

Notas

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

Recomendações

criar os mesmos estados no Xray antes da migração
links diferentes Test<=>Defect Test<=>Requirement
backup Jira before migrating
After working hours (as it can be intensive)

O que migra

(Zephyr) Test => (Xray) Test
Cycle => Test Plan (optional)
- plus 1 Test Execution (Executions soltas)
Cycle's folder => Test Execution
- name of the folder in the Summary
- <version> - <cycle's name> - <folder> Execution
**Ad-hoc Cycle => Test Plan (optional)
- plus 1 Test Execution
Execution => Test Run

fixVersion é inferido da versão atribuída ao cycle

Test Plan

Requisitos iniciais

Pós-operações

??

The current importer is relatively basic. If you need to migrate more information and have further control over the migrated data, we recommend you contact an Atlassian partner with expertise on this kind of migrations. Note that migrating "all" information may be a complex process to implement and some things may not be mappable at all.

The steps information from HP ALM/QC is saved in HTML which is only convertible to Jira's wiki markup from Jira 7.2 and later. In Jira version below 7.2, the steps are shown with HTML markup.
In order to import Tests, the Test issues cannot have required fields in Jira; you must set them as optional before starting the import process.

How to use

Suppose you have a project in HP ALM (see above for supported version/s) and you wish to import the tests from HP ALM's "Test Plan", as seen below:

To start the importation process:

Log in with an administrator account.
Go to System>Import and Export>External System Import.
Select Xray's HP ALM/QC Importer.

Then, you need to fill out the details of the HP ALM/QC instance, including its host name/IP, port, domain, project and authentication credentials.

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.

Then, you need to choose the project in which you want the Test issues to be created.

A final confirmation dialog presents information about the total number of Tests that will be imported.

This number may be lower than the actual number of Test issues that will be created; this occurs because Xray will only be able to import some of the tests, depending on their characteristics which can only be determined during the actual importation.

At the end, a brief summary is shown mentioning the total number of Test issues created and any warnings that occurred during the process.

From this screen, you can also see the list of created issues based on the label you provided. You can also consult the detailed logs about the process.