Issue Summary

JCMA migrates Automation "Edit Issue" actions with "Copy" or "Add" operations resulting in fieldType: null and silent failure

• Source: Jira Data Center / Server (v10.7.4)

• Destination: Jira Cloud

• Tool: Jira Cloud Migration Assistant JCMA v1.12.49

• Scope: Global and Project-scoped Automation Rules

Steps to Reproduce

1. In Jira Server/DC, create an Automation for Jira (A4J) rule with an Edit Issue component.
2. Configure a custom field in this action to use the "Copy from issue" or "Add to issue" operation (e.g., Target Field = Copy [Source Field] from Current Issue).
3. Migrate the project containing this rule to Cloud using JCMA.
4. In Cloud, open the migrated Automation rule and inspect the "Edit Issue" component.
5. Export the Cloud automation rule to JSON to inspect the sourceField object.

Expected Results

The rule migrates with the Source Field correctly selected in the UI. The underlying JSON should contain both the Field ID and the correct fieldType (e.g., com.atlassian.jira.plugin.system.customfieldtypes:userpicker).

Actual Results

The "Copy from" dropdown in the Cloud UI renders as empty/blank. The rule fails silently at runtime because the field type is missing.

The exception below is thrown in the Cloud Automation Rule JSON export:

"sourceField": {
  "type": "ID",
  "value": "customfield_10905",
  "fieldType": null   <-- CAUSE OF FAILURE
}

Workaround

Open the affected rule in Cloud, edit the "Edit Issue" component, manually re-select the correct Source Field in the "Copy from" dropdown, and publish the rule.