How to migrate automation rules

When migrating to cloud using the Jira Cloud Migration Assistant, you can migrate your automation rules along with other project components. This page explains what automation rules you can migrate and how they work after migration.

はじめる前に

• Ensure the Automation for Jira plugin (version 7.2.6 or later) or Automation for Jira Lite plugin (version 7.3.3 or later) is enabled in your Data Center instance.

• Review your automation rules, especially those with cross-project dependencies

• Understand that some components may need reconfiguration after migration

• The following features are not included in migration:

  • 自動化監査ログ

  • Performance insights

  • Global configuration settings

Understanding automation rules

Before migration, it's important to understand two types of automation rules:

• Project rules: Specific to individual projects

• Global rules: Apply across multiple projects

移行オプション

When migrating automation rules, you have three options:

Option 1: Only automation rules related to selected projects

• Migrates rules specific to your selected projects

• Does not include global rules

• Includes option to include or exclude disabled rules

Option 2: All automation rules

• Migrates both project-specific and global rules

• Only option that includes global automation rules

Option 3 : None

• No automation rules will be migrated

Key migration behaviors

• Rules referencing multiple projects will work partially until all referenced projects are migrated

• Users and groups mentioned in rules are automatically included in migration

• All migrated automation rules are disabled on the cloud by default post migration

Automation components supported in migration

When migrating automation rules, components have different levels of support in cloud. Here's what each status means:

• Supported components: Migrate completely and work the same way in cloud

• Partially supported components: Migrate but may have some limitations or behave differently in cloud

• Unsupported components: Don't migrate and need to be recreated in cloud

Review your automation rules before migration to identify any using partially supported or unsupported components.

Fully supported components

These components migrate with complete functionality and work as expected in cloud:

Partially supported components

Partially supported components migrate to the cloud but might exhibit differences in functionality due to feature parity between Jira on-premise and cloud environments. This means that certain features or settings available on-premise may not exist or behave differently in the cloud, resulting in a slightly altered user experience.

It's important to verify each component post-migration to ensure it functions as expected. If you notice any discrepancies, you can manually adjust settings to align with your original setup.

What You Can Do:

• Review and test: After migration, review all partially supported components and test their functionality in the cloud environment.

• Manual adjustments: For any differences observed, manually reconfigure the components to match your needs.

Unsupported components

These components won't migrate and need to be recreated in cloud if needed:

詳細情報とサポート

移行をサポートする多数のチャンネルをご用意しています。

• 移行の詳細な計画情報や FAQ については、Atlassian Cloud 移行センターを参照してください。

• 技術的な問題が発生していたり、戦略やベスト プラクティスで支援が必要な場合、お問い合わせください。

• 専門的なアドバイスについては、アトラシアン コミュニティもご利用ください。

• 専門家によるサポートが必要な場合は、アトラシアン パートナーにご相談ください。