Alert actions and policies after migration
Alert actions and policies in Opsgenie transition to Jira Service Management with structural updates and feature changes. While alert policies are auto-synced, you might need to review your workflows and configurations for action policies and deprecated notification policies.
Migration summary
Is this feature fully available in all Jira Service Management plans?
No, feature availability varies based on your selected product and plan:
Alert policies are available in Jira Service Management Premium and Enterprise plans.
Notification policies are available in Jira Service Management Premium and Enterprise.
Action policies are also available in Jira Service Management Premium and Enterprise plans and have been upgraded to Atlassian Automation (A4J).
Is this feature auto-synced after data migration?
Alert policies are fully migrated and automatically synced.
Notification policies are also fully migrated and automatically synced, unless you’re using the deprecated version of notification policies.
Action policies aren't migrated. In Jira Service Management, you can recreate them using Atlassian Automation.
Are there required actions for full workflow parity?
Yes. For a full workflow parity you should:
If you’re using the old version of notification policies, update to the new notification policies in Opsgenie before migrating to ensure they sync properly.
Recreate action policies in Jira Service Management using Atlassian Automation.
Update notification policies before migration
If you're using a deprecated version of notification policies, they won’t be automatically migrated to Jira Service Management. You must manually update them to the latest version before migration. This is a one-time action that converts your global notification policies into team-based notification policies.
Follow these steps to update your notification policies:
In Opsgenie, go to Settings > Global policies
Select Migrate to V2. This action will convert all your global notification policies into team-based policies, categorized as Auto-close, Suppress or Delay rules.
Go to Teams > Policies to review the migrated policies assigned to each team.
Once you complete these steps, your notification policies will automatically sync with Jira Service Management, depending on your migration destination.
Recreate action policies using Atlassian Automation
Although alert actions are deprecated, you can recreate them using Atlassian Automation to maintain similar functionality. To do this:
Go to Teams > Operations > Automation.
Select Create automation. This will open the rule creation screen with alert-based triggers pre-selected. Read more about Jira automation triggers.
Configure the rule to match your previous action policy by defining the trigger, conditions, and corresponding actions.
Save and test the automation to ensure it behaves as expected.
Was this helpful?