Atlassian stopped selling Opsgenie on 4 June 2025, and on 5 April 2027 it will shut off access and delete customer data that hasn't been migrated. Atlassian's own path is Jira Service Management or Compass. Whatever you choose, your on-call rota (who's on when, the rotation rules, the swaps people agreed) is the part teams rebuild by hand, so export it while you can.
Free tool: Plan a fair rota: leave, public holidays, weighted fairness and an .ics calendar
Runs in your browser. Public holidays come from Nager.Date; change any shift and the fairness tally updates.
GET /v2/schedules?expand=rotation lists them all; GET /v2/schedules/{id} includes each rotation's participants and time restrictions.GET /v2/schedules/{id}/timeline?expand=base,override&interval=3&intervalUnit=months. This is who was really on call, after swaps.GET /v2/schedules/{id}.ics returns the schedule as .ics, which nearly every other tool and calendar can read.api.eu.opsgenie.com instead of api.opsgenie.com.Export the past 12 months of timeline too. It's the only record of how on-call load was actually shared, which you'll want when someone asks whether the rota is fair, or when the new tool's rotation doesn't match what people were used to.
Free tool: Plan a fair rota: leave, public holidays, weighted fairness and an .ics calendar
Runs in your browser. Public holidays come from Nager.Date; change any shift and the fairness tally updates.
How does your team decide who's on call today, and what went wrong with the rota last time (a holiday, a swap, an unfair month)?
We're researching this problem and read every answer. Tell us what happened (4 short questions, no sign-up; AI tools help us read the answers).