Issue Summary

When migrating automation rules from Jira Data Center to Jira Cloud via JCMA, status references in conditions and transitions often fail to bind to Cloud status objects. Even if the statuses exist in Cloud, the rules retain raw DC numeric IDs (e.g., 12345), resulting in "Value unavailable" errors. 

Steps to Reproduce

1. Create Automation rules in Jira DC using Status conditions or Transition actions.
2. Migrate the project and rules to Jira Cloud using JCMA.
3. Open the migrated rules in Jira Cloud Automation settings.

Expected Results

JCMA should automatically map all DC status IDs to the corresponding Cloud status objects, ensuring rules are functional post-migration.

Actual Results

Rules are migrated with unresolved status references, appearing as "broken" in the UI and failing to execute.

"Destination status could not be resolved."

Workaround

Manual remediation is required:

1. Identify affected rules via the post-migration report.

1. Manually re-select the correct status in the Cloud Automation UI for each broken component.

1. Save and Publish the rule.