On-call schedules after migration

The core functionality of on-call schedules remains largely the same in Jira Service Management, but there are key differences in how they work in each product. While most features operate similarly to Opsgenie, there are UI changes and feature-specific details to be aware of.

Migration summary

Are on-call schedules available across all Jira Service Management plans?

Yes, on-call schedules are available in all plans with minimal UI changes. You can also find global integrations in Operations > On-call schedules.

Are on-call schedules auto-synced after migration?

Yes, on-call schedules are automatically synced in Jira Service Management. No manual action is required.

Are there required actions for full workflow parity?

No major actions are required, but users should review the changes below to understand UI and workflow differences. 

What has changed?

The following changes apply to Jira Service Management:

• Users must launch Operations for an Atlassian team first before creating team-based on-call schedules. Otherwise, schedules can be used without teams. 

• Opsgenie Groups aren’t supported. Users need to replace groups with Opsgenie Teams to ensure schedules migrate properly.

• New schedule templates are available in Jira Service Management, helping teams create on-call schedules faster.

Limits to escalation policies

At the team level, a single team may have up to 300 policies, with each policy containing as many as 50 rules.

On-call schedules in Jira Service Management

To access on-call schedules in Jira Service Management, go to Operations > On-call schedules in the side menu. View who is on-call, shift durations, and team rotations. Manage global on-call schedules and team-specific rotations.