Kayabyte

Opsgenie to Jira Service Management: on-call pay reports

By Kayabyte · Updated 12 November 2026

Short answer: Opsgenie is shut down on 5 April 2027 and its on-call schedules move to Jira Service Management Operations. Schedules, rotations and overrides come along, but if payroll gets on-call hours from Opsgenie reports or exports today, plan the replacement before the switch: Jira Service Management shows the on-call timeline but has no standby pay report per person, and its API only lets people, not apps, read schedules. On-Call Pay is a Jira app that fills that gap.

What moves, and what to check

The API detail that matters

Reading schedules and timelines through the Jira Service Management Operations API works with a person’s access. Calls made as an app are refused (“Account does not have access to Opsgenie”). Any tool that builds pay reports has to run as a person: interactively as the viewer, or, for an automatic monthly run, as a named admin.

Keep payroll numbers stable

  1. Agree the pay rules in writing: categories (office hours, outside office hours, weekends, public holidays), rates, time zone, working days and holidays.
  2. Run one month in parallel: the old Opsgenie numbers and the new Jira Service Management numbers. Differences are usually time zones, overrides or holidays.
  3. Save each month’s report when it goes to payroll, so it can be shown again later with the same numbers.

Doing it in Jira

On-Call Pay reads the final on-call timeline of your schedules, splits each person’s time into office hours, outside office hours, weekends and public holidays in your time zone, applies hourly standby rates, and gives hours and pay per person with a CSV for payroll. On the 1st it can save last month’s report as a snapshot. It is in review at the Atlassian Marketplace. For the manual method, see How to calculate on-call pay from Jira Service Management schedules.

Jira, Jira Service Management, Opsgenie and Atlassian are trademarks of Atlassian. Kayabyte is an independent developer and is not affiliated with or endorsed by Atlassian.