Issue Summary
When migrating automation rules from Jira DC to Cloud via JCMA, the JSM Organization field (com.atlassian.servicedesk:sd-customer-organizations) within Edit issue (jira.issue.edit) action components does not follow the entity transformation pipeline (MMS).

Instead of mapping the DC Organization ID to the new Cloud Organization ID, the raw numeric ID from the source is migrated. This leads to two failure scenarios:

1. Data Corruption: If the source ID (e.g., "100") happens to exist on the Cloud site but represents a different organization, the automation rule will incorrectly link to that unrelated organization.
2. Functional Failure: If the source ID does not exist on the Cloud site, the field is left blank/null in the migrated rule.

Steps to Reproduce

1. On Jira DC, identify a JSM organization (e.g., ID 100).
2. Create an automation rule with an Edit issue action that sets the Organizations field to this organization.
3. Migrate the project to Cloud using JCMA.
4. Inspect the migrated rule in Cloud.

Expected Results
The Organization ID 100 from DC should be translated to the corresponding Cloud Organization ID (e.g., 12) based on the MMS mapping store.

Actual Results
The rule arrives in Cloud still referencing ID 100.

• If ID 100 does not exist in Cloud, the field appears empty.
• If ID 100 exists in Cloud (but is a different organization), the rule is saved with the wrong organization.

Workaround
Manually audit and update all Automation rules in Cloud that use the "Edit Issue" action to ensure the Organizations field is pointing to the correct Cloud entity.