Page History
...
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. |
|
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
...
- plus 1 Test Execution (Executions soltas)
...
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
|
fixVersion é inferido da versão atribuída ao cycle
Test Plan
|
...
Requisitos iniciais
Pós-operações
...
| ||
Execution
| Test Run
|
Info | ||
---|---|---|
| ||
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. |
Info | ||
---|---|---|
| ||
|
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:
All issues will be created in the project where the migration is being performed. |
How to use
Migrating data is easy; however, it is currently limited to Jira administrators.
The migration follows a wizard like interface; after going through the steps, some additional tasks required to ensure consistency of data.
Performing the migration
Suppose you have a project that you wish to migrate from Zephyr for Jira to Xray.
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 Importers Zephyr 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.
...
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.
After doing the migration
After migrating data from Zephyr to Xray you will need to perform some additional operations:
- ??
- ???