Requirement Module Migration
In Zephyr Enterprise, requirements and folders exist at both the project and release levels, with an option to sync between them. In QMetry, all requirements and folders are maintained only at the project level.
During migration, QMetry moves requirement folders from the project level in Zephyr Enterprise to the corresponding project. It does not keep release-level associations. During migration, QMetry associates requirements with the corresponding release from Zephyr Enterprise and links them to the default cycle.
Requirement and Requirement Folder Structure Migration
The Requirement and Requirement Folder Structure are migrated as follows:
Internal Requirements
QMetry migrates all internal requirements from Zephyr Enterprise as Internal Requirements. Each requirement is linked to its corresponding release.
Priority values in Zephyr Enterprise differ from those in QMetry. After migration, the priority field is mapped to match the QMetry format as follows:
Zephyr Enterprise Priority Name
QMetry Priority Name
P1
Blocker
P2
Critical
P3
Major
P4
Minor
P5
Trivial
Jira Requirements
The following table summarizes key aspects of the Jira Sync requirement:
Feature | Zephyr Enterprise | QMetry |
|---|---|---|
Jira Requirement Import | Supports two methods:
| Import requirements at the Project Level require mapping Jira Project and Issue Type to QMetry Project. |
Folder Structure | Folder structure is defined per release, using Jira fields as folder names. | The folder structure is custom-defined at the project level. |
During migration, QMetry transfers the folder structure from the project's latest release, which uses Jira Sync. If the project does not use Jira Sync, all requirements migrate under a folder named after the corresponding Jira project.
Migrating Jira Requirement
Each Jira work item migrates as a unique requirement for QMetry. Test cases linked to multiple instances of the same Jira work item in Zephyr Enterprise are consolidated and related to the corresponding single requirement in QMetry.