PagerDuty-based rotations
In Pro mode, you can create PagerDuty-based rotations. A PagerDuty-based rotation is a rotation where the members and the user on duty comes straight from a PagerDuty schedule and not from RoundRobin.
The main benefit is that you can rely on all the other Slack integrated features of RoundRobin without the complexity of doing cross-management of duty shifts in PagerDuty and RoundRobin at the same time.
To work with PagerDuty, you first need to connect PagerDuty to RoundRobin. Please follow the instructions here.
Create a PagerDuty-bound rotation
Let's make an example.
Let's say you have a schedule called Service X, where you manage the duty responsibility for a certain service in your organization (is just an example - we expect your schedule to have more than one user!).
You can now create a rotation in Round Robin called Service X (name is not important) and connect it to PagerDuty from Slack using the "Manage Integrations" function.
- Create an empty rotation. Do not bother yourself adding members as everything will be managed automatically. You can still add channels or topics.
- Go to "More Actions" and choose "Manage integrations...".
If PagerDuty is not available or the app is not running in Pro mode, you will a message to inform you you cannot use this function.
- Choose PagerDuty from the dropdown and search between PagerDuty schedules directly from Slack.
- After Submit the rotation will become a PagerDuty-bound rotation; you will not be able to edit members or groups, but you will still be able to manage other aspects, like the on-duty group or the templates (from the web app).
- After the first sync, the rotations members will match the PagerDuty schedule members and the current user on duty in the schedule will go on duty in Round Robin as well.
Match is done by email address. If the users list is not a match, verify that the PD email addresses matches the email addresses of your users in Slack.
- If the schedule changes, the same will happen to the rotation (new members, removed members, different user on duty). The sync happens every minute - it's not real time.