Key Considerations

The following have not been migrated from Zephyr Enterprise to QMetry.

Details

Descriptions

URL

The URLs will be updated after migration.

User

Type, Location, Title, Address, Country, State, City, Zip Code, and Phone will not migrate.

Project

  • Project-level custom values will not migrate. Data will move to the project description.

  • All projects will migrate as Normal. Normal, Isolated, and Restricted settings will not migrate.

  • Project Start Date and End Date will not be migrated.

  • Attachment storage configuration will not be migrated.

Release

  • A numeric prefix will be added during migration if a duplicate release name exists.

  • Project Test Repo Release and Global Release will not migrate as releases. However, the data will migrate at the project level.

Cycle

A numeric prefix will be added during migration if a duplicate cycle name exists.

Custom Fields

Checkbox custom values will convert to a drop-down list with options True and False.

Requirement

  • Folder structure at the release level will not migrate. Only project-level folder structures will migrate.

  • Jira import folders will not migrate.

  • Only the latest Jira sync folder will migrate. All Jira requirements will map to this folder.

  • JQL queries in Zephyr will not migrate. All Jira requirements will map to the folder structure.

  • Requirements at the import level will not migrate.

  • Only unique Jira requirements will migrate. Duplicate Jira requirements will be ignored.

  • Issues other than Bug or Defect will import as requirements. These will link to test cases where the Jira issue is attached as a defect, with the execution comment containing the Jira link.

  • Bug or Defect issues in the requirements module will convert to internal requirements in QMetry, with the defect or bug linked to the requirement.

Testcase

  • Test case types (Original, Shared, Imported) will not migrate.

  • Estimated times of less than 1 second will migrate as 1 second.

  • The Automation checkbox will convert to a select list with options True and False.

  • Test step details that exceed 65,535 characters will be truncated.

  • Call-to-Test relationships will migrate as shareable tests. Multiple hierarchies will merge into a single shareable test.

  • Duplicate folder names at the same level will include numeric prefixes.

  • Parameter data grids are defined at the execution level, not the test case level.

  • Parameters with the same name will merge into one.

  • Step parameters not found in the data grid will convert to plain text.

  • Shared test cases between projects will create duplicates in the target project, preserving the respective shared versions.

  • Test cases from the global repository will appear only in the shared Test Suite Execution section of the project; they will not appear in the project repository.

  • All parameters in the data grid will be added to the first step's Test Data box after migration.

Planning and Execution

  • Planned but unassigned test cases will not link to the test suite.

  • For test cases assigned to Anyone:

    • If executed, the assignee will appear as Executed By.

    • If not executed, the assignee will change to Unassigned.

  • Step execution data will not migrate if the execution status is not Pass for parameterized or Call-to-Test executions.

Internal Issues

  • Target milestone will not migrate.

  • If defect tracking switches from Internal to Jira, internal defects will not migrate.

  • Defect IDs will change after migration.

External Jira Issues

  • All relevant values from Jira will migrate to QMetry.

  • Internal ID, Created Date, Defect Status, Category, Created Date Time, Modified Date Time, and Created By values from Zephyr will not migrate.

Other

  • Audit logs will not migrate. You can download them from Zephyr.

  • Automation custom parsers will not migrate.

  • Groups will not migrate.

Publication date: