Integrate Jira Service Management with Round Robin

Connecting Jira Service Management lets Round Robin read your operations schedules, so you can create rotations whose members and on-duty user come straight from Jira. You set up and manage the connection on the Round Robin dashboard, under Settings > Integrations. The connection uses an Atlassian API token belonging to one account (there is no OAuth flow).

Before you start: create an API token in Atlassian

The token belongs to a person’s Atlassian account, so pick the account carefully: Round Robin reads schedules as that account, and can only see what it can see.

1. Open Atlassian account settings and go to Security > API tokens.
2. Click Create API token with scopes.
3. Give the token a name, then choose the Jira app. The operations scopes live there; there is no separate Jira Service Management entry.
4. Grant the read scopes for on-call schedules, then create the token.
5. Copy the token. You will paste it into Round Robin in the next section, and Atlassian will not show it again.

Connect Round Robin to Jira Service Management

1. Open the Round Robin dashboard and go to Settings > Integrations.
2. On the Jira Service Management card, click Connect.
3. Fill in the dialog:
   • Site: the acme of acme.atlassian.net. Pasting the full URL works too.
   • Atlassian account email: the account the token belongs to.
   • API token: the token you just created.
4. Click Connect.

Once connected, the card shows a Connected badge and the last digits of the stored token. From here you can also Edit credentials to rotate the token without disconnecting.

With the connection in place, you can bind rotations to Jira Service Management schedules. See PagerDuty, OpsGenie and Jira Service Management based rotations.

Tell Round Robin who each responder is in Slack

Jira hides email addresses by default, for every account type. Round Robin normally matches an external schedule’s participants to Slack people by email, so on most Jira sites it will match nobody, and a responder it cannot place goes on duty with no one to mention in Slack.

Set them by hand instead, once per person:

1. Open the rotation and go to the Roster tab.
2. For each participant, pick who they are in Slack.

A mapping you set by hand wins over the email match and survives every later sync, so this is a one-off per person rather than something to redo. See External rotations for how the roster behaves.

Disconnect Jira Service Management

1. Go to Settings > Integrations in the Round Robin dashboard.
2. On the Jira Service Management card, click Disconnect and confirm.

Disconnecting unbinds every rotation

Disconnecting unbinds every rotation that is linked to a Jira Service Management schedule. Those rotations switch to manual mode, and each rotation’s owners receive a Slack message telling them the rotation is no longer bound.

Coming from Opsgenie

Atlassian is closing Opsgenie on 5 April 2027 and moving its customers to Jira Service Management. Round Robin supports both, and your OpsGenie connection keeps working until Atlassian turns it off, so there is no rush: connect Jira Service Management when your own Atlassian migration happens, rebind your rotations to the Jira schedules, then disconnect OpsGenie.

Next steps

• PagerDuty, OpsGenie and Jira Service Management based rotations: link a rotation to a schedule now that Jira Service Management is connected.
• External rotations: how the sync behaves, and what it takes over.