Jira automation rules do not migrate themselves

Описание и применение

Правила автоматизации Jira не мигрируют автоматически и остаются отключенными, требуя ручного назначения акторов и включения через API.

Задача

Automation rules are not migrated or are disabled after Data Center to Cloud or Cloud to Cloud migrations, requiring manual actor assignment and enabling via API.

Результат

Automation rules can be restored to a functional state by setting actors and enabling them via the Rule Management API after migration.

Рабочий процесс

• Identify migration type (DC→Cloud or Cloud→Cloud).
• Verify rules exist post-migration (DC→Cloud) or export them manually if needed.
• Use Rule Management API to list rules via /rule/summary with cursor-based pagination.
• For each rule, determine the correct actor by querying accountType == 'app' rather than prefix.
• Update the rule’s actor using the API, ensuring the actor exists in the target site.
• Enable the rule via the API.
• Verify rules fire correctly.
• Audit the migration to confirm all rules are active and correctly configured.

Доказательства

Flow actors are not migrated.

Источник

All migrated automation flows are disabled on the cloud by default post migration.

Источник

Automation flows (including project-level automation flows).

Источник

GET /rest/v1/rule -> 404 GET /rest/v1/rule/summary -> 200