Problem Definition

Currently, when migrating Automation rules from Jira Data Center to Jira Cloud, any rules containing Slack actions are not supported and will not be migrated. As documented in How to migrate automation rules, Slack actions must be manually recreated in Jira Cloud after migration. This limitation creates significant manual overhead, increases the risk of misconfiguration, and disrupts established notification workflows for teams that rely on Slack integrations within their automation.

Suggested Solution

Enhance the Jira migration process to support the export and import of Automation rules containing Slack actions. Specifically:

• Extend the migration tool to recognize and transfer Slack actions within Automation rules from Jira Data Center to Jira Cloud.

• Where possible, automatically map Slack channels and actions to their equivalents in the Cloud environment.

• Provide clear reporting or guidance for any actions or channels that cannot be mapped, so administrators can address them efficiently.

Why this is important

• Reduces manual effort and risk of errors by automating the migration of complex Automation rules that include Slack actions.
• Ensures continuity of critical communication and notification workflows, minimizing disruption to teams during migration.

• Supports organizations in adopting Jira Cloud by removing a significant barrier for those who rely on Slack-integrated automation.

• Aligns with best practices for cloud migration by providing a smoother, more automated transition path for key integrations.