Skip to content

PagerDuty and Jira Service Management rotations

ProThis feature needs a Pro plan. On Free the settings are visible but locked.

A PagerDuty-based rotation follows the people and shifts of a PagerDuty schedule. Round Robin shows those assignments in the dashboard and uses each person’s Slack mapping for mentions and notifications.

For a Jira Service Management schedule, follow Connect a rotation. The steps and examples below are for PagerDuty.

You need: PagerDuty connected to your workspace, an enabled rotation and permission to edit it.

  1. Open the rotation in the dashboard.
  2. Go to Settings → Integrations → External schedule.
  3. Under Which product, choose PagerDuty.
  4. Use Search Schedules to find the schedule, then select it under Schedule.
  5. Check the Person, Start, End and Status columns in the assignment preview. Expand Schedule members to see the participants.
  6. Click Connect this schedule.

The rotation page opens. Schedule sync pending shows while the first assignments load, which takes about a minute. Leave the page open, or click Refresh to check again.

The picker lists classic and shift-based PagerDuty schedules alike, with nothing to choose between them.

The schedule decides the participants, shift times, recurrence and overrides, and the hours the rotation covers. Change them in PagerDuty. The rotation has no Round Robin lanes or coverage windows to configure.

The rotation is on call whenever the PagerDuty schedule has somebody assigned. Its Coverage tab says so in a note headed Hours set in PagerDuty.

To cover only part of the day or week, change the schedule in PagerDuty:

PagerDuty schedule What to change
Classic Add restrictions to the schedule’s layers, for example weekdays 09:00 to 17:00.
Shift-based Set the shift times to the hours you want covered.

Outside those hours nobody is assigned, and Current duty reads No scheduled assignment.

Open People & Groups. The linked to Slack count shows how many participants have a Slack account. Each participant is marked Matched by email, Set manually or Not in Slack.

A participant without a Slack mapping still appears on their shift, but cannot be mentioned in Slack. Use Pick person to choose their Slack account. See Say who a participant is in Slack.

A manual mapping stays in place when that participant’s shifts change. Mapping one person changes nobody else’s mapping.

Current duty lists the current assignments, each with its own start and end. Next change gives the time of the next change, then splits it into Starting assignments, Ending assignments and Continuing assignments. Starting and continuing assignments show their end under Until.

Somebody starting a shift does not always replace everybody already on call. A follow-the-sun schedule can have these weekday shifts, shown here in Berlin time in September:

Time People on call
09:00 to 15:00 Berlin participant
15:00 to 17:00 Berlin participant and two US participants
17:00 to 23:00 Both US participants
23:00 to 09:00 No scheduled assignment

At 15:00 the US assignments start and the Berlin one continues. At 17:00 only the Berlin assignment ends. The two US participants stay on call until 23:00.

A workweek and weekend schedule has one assignment at a time instead: the workweek participant hands over on Friday at 17:00, and the weekend participant hands back on Monday at 09:00. Both patterns come from PagerDuty, time zone and daylight saving included.

Open Plan and choose Timeline or List. Both show the assignments for the selected dates, overlapping assignments and participants without a Slack mapping included.

In Timeline, overlapping shifts sit on separate rows. Select an assignment to read its Start, End and Time zone. The rows only separate the shifts on screen; they are not schedule settings.

Earlier, Later and Today move through the dates. Only my shifts highlights the shifts mapped to your Slack account and keeps the others visible. Times are shown in the zone chosen under Times in the page header.

Past dates show the assignments Round Robin recorded. For anything before the rotation was connected, open the schedule in PagerDuty.

View in PagerDuty on Coverage opens the linked schedule.

Open History to see recorded duty and the assignments still running.

What you see What it means
A provider name or email address The participant has no Slack mapping.
Unknown person The record cannot identify who held the duty. Somebody was still on call.
Unnamed The participant is recorded with no name or email to show.

Use the person filter to pick a participant, or choose Everyone to clear it. CSV and JSON exports hold the completed duty for the selected filters. A running assignment is exported once its duty is recorded as complete.

What you see What to do
Schedule sync pending The first sync has not finished. Leave the page open or click Refresh.
Schedule sync unavailable The first sync could not be confirmed. Click Refresh. If it stays, check the PagerDuty connection under workspace Settings → Integrations.
Not in Slack The participant has no Slack mapping. Choose their account on People & Groups.
Unassigned PagerDuty has a shift with nobody on it. Assign somebody in PagerDuty if the shift needs cover.
No assignments in this preview The schedule has no current or upcoming assignments. Check its dates in PagerDuty.
No scheduled assignment The schedule has nobody assigned at this time, which is expected outside its restrictions or shifts. If somebody should be on call, check the schedule in PagerDuty.
Schedule data stale The saved assignments cannot be confirmed as current. Check PagerDuty and the workspace connection before relying on them.
Schedule unavailable or Coverage unavailable Current coverage cannot be confirmed. Check the PagerDuty connection under workspace Settings → Integrations.
Plan unavailable The selected dates did not load. Click Try again. If it keeps failing, check the connection.
No known next change The schedule shows no further change. Look at later dates in Plan, or open PagerDuty.
Next change unavailable The next change cannot be confirmed. Check the connection and the schedule in PagerDuty.

An unavailable schedule does not mean nobody is on call. A stale result can still show when known assignments end without confirming who starts next.