How it works

Which time counts

On-Call Pay reads each schedule’s final on-call timeline from Jira Service Management: the rotations with overrides applied, as recorded. Only time that has already passed counts. Time from before a schedule existed is not included, because Jira Service Management has no history for it.

When a team or escalation is on call, the people it resolves to are counted.

Categories

Each on-call hour falls into one category, in the pay plan’s time zone: - Public holiday: a public holiday of the chosen country (and state or region), all day, also on a weekend. - Weekend: a day that is not one of the working days. - Office hours: on a working day, between the office hours start and end. - Outside office hours: the rest of a working day (mornings, evenings and nights).

Daylight saving changes are counted as they happened: the night the clocks go back has one hour more.

Pay

Pay is hours in a category times that category’s hourly rate, summed per person. Amounts are calculated from the exact time and rounded to whole cents or øre once per category.

If someone is on call in two schedules at the same time, that time is counted once.

Monthly snapshots

On the 1st of each month the report for last month is saved for the chosen schedules, using the access of the admin who turned snapshots on. Snapshots are kept for 24 months. If the run fails (for example the admin lost access to a schedule), the settings and the snapshots tab say why, and it tries again the next day.

What On-Call Pay stores

The pay plan, the snapshot settings (including the account ID of the admin the monthly run acts as) and up to 24 monthly snapshots (account IDs, display names, hours and amounts per person). It does not store alerts or schedule contents. See the privacy policy.