Advanced alert configurations after migration

Advanced alert configurations in Opsgenie include heartbeat monitoring, audit logs, global custom roles, and role-based notifications (previously called central notification templates). These features remain available in Jira Service Management but have new limits and configuration changes.

Migration summary

Is this feature fully available in all Jira Service Management plans?

No, some advanced alert configurations are only available in higher-tier plans:

• Heartbeat monitoring isn't available in Jira Service Management Free and Standard plans.

• Global custom roles and role-based notifications aren't available in Jira Service Management Free and Standard plans.

Is this feature auto-synced after data migration?

• Heartbeats, audit logs, and role-based notifications will be moved automatically.

• Heartbeats exceeding the 2,000 limit per site will still be moved, but you must remove excess heartbeats in your new product before adding more.

• The Owner role template in central notification templates (now called Role-based notifications) won’t be migrated as this role no longer exists in Jira Service Management.

Are there required actions for full workflow parity?

Yes. You’ll need to:

• Update heartbeat email references in scripts to match new Jira Service Management domains. Heartbeat names are updated to the new atlassian.net servers and will continue to function as usual. However, if there are scripts you’re using the heartbeat names with the opsgenie.net servers, we recommend updating your scripts.

• Manually recreate deprecated heartbeats if they were using the older version of Heartbeats (Heratbeats v1).

• Remove excess heartbeats if their migrated total exceeds the 2000 cap.

• Reassign role-based notifications previously assigned to the Owner role.

Advanced alert configuration in Jira Service Management

Heartbeats

Currently, heartbeats are only available for your teams. You can access your hearbeat from your team’s operations. To find your updates and review them;

1. Go to Teams > Operations > Heartbeats to view your migrated heartbeats.

2. If your site has more than 2000 heartbeats ask your Jira admin to remove excess heartbeats from other teams' operations.

3. Since heartbeat emails are changed we recommend updating email references in scripts to reflect Jira Service Management domains. Select Copy heartbeat name from the Actions menu to copy the new email for your heartbeat.

4. If any heartbeats weren’t migrated due to outdated formats, manually create a new heartbeat using Jira Service Management’s API.

Read more about heartbeats in Jira Service Management

Central notification templates

Templates assigned to the Owners in Opsgenie are now disabled, as your Opsgenie owners have been mapped to a different role in Jira Service Management. You can either reassign these templates to an Admin, or remove them if an existing admin role template is already in place.

1. Go to Operations > General configuration > Role-based notifications.

2. Locate templates that were previously assigned to the Owners role.

3. Reassign the template to an Admin role, or remove it if an existing admin role template is already in place.

Read about setting up role-based notifications in Jira Service Management.

Audit logs

Audit logs related to Operations, such as alert logs, notification logs are located seperate from Jira logs. You can find them under Operations > General configuration > Audit logs. Read more about audit logs.