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