DC to Cloud migration creates duplicate custom Test and Test Step statuses instead of merging them with existing Cloud statuses

Summary

DC to Cloud migration creates duplicate custom Test and Test Step statuses instead of merging them with existing Cloud statuses.

Description

When migrating Xray data from the Data Center to the Cloud, custom Test or Test Step statuses that already exist in the Cloud with the same name are recreated with a _migrated suffix, sometimes followed by a number.

The migration should map these statuses to the corresponding existing Cloud statuses instead of creating duplicates.

Preconditions

• A custom Test or Test Step status exists on the Data Center.

• A corresponding custom status with the same name and type already exists in Cloud.

Steps to Reproduce

1. Create a custom Test status on Data Center, such as ABORTED or BLOCKED.
2. Create a Test status with the same name in Cloud.
3. Perform an Xray DC to Cloud migration using JCMA.
4. Review the migration report and the status configuration in Cloud.

Actual Result

The migration creates new statuses with modified names instead of reusing the existing Cloud statuses.

Expected Result

Custom statuses should be mapped to existing Cloud statuses when their names and status types match. No additional statuses with a _migrated suffix should be created in this scenario.

Impact

Duplicate statuses are introduced into the Cloud configuration, requiring manual review and cleanup and potentially affecting status consistency in reporting and execution workflows.

Workaround
You can merge them manually. To do that, go to Jira Settings > Apps > Xray Settings > Test Statuses, then delete the status with the _migrated suffix (ex.: ABORTED_migrated). On the deletion screen, you'll be prompted to select a replacement status to apply across all affected test runs, so at that point, select the original status (i.e., ABORTED). This will consolidate all Test Runs under the single status.