Opsgenie (and Jira Service Management operations)

Proofroom reads on-call schedules and incidents from Opsgenie, or, once your account has moved, from Jira Service Management operations.

Opsgenie shuts down on 5 April 2027. Atlassian then switches Opsgenie off and deletes any data that has not been moved to Jira Service Management (Atlassian’s announcement). While the integration’s platform is opsgenie, the connection test and every evidence summary say so.

To switch:

1. Move your Opsgenie account to Jira Service Management with Atlassian’s migration tool, well before the date.
2. Set up the Atlassian account and API token described under Jira Service Management operations.
3. In Proofroom, open the Opsgenie integration, edit its configuration: set Platform to jsm and fill in Site, Email, API token and Incident JQL. The Opsgenie API key is no longer used.
4. Press Test connection, then save. Evidence already filed stays as it is; later runs read Jira Service Management.

What each collector shows

Opsgenie

An account owner or global admin: Settings → API key management → Add new API key, with Read and Configuration access (schedules are configuration; Proofroom never writes). The Incident API needs the Standard or Enterprise plan; on Essentials or Free, Incident timelines fails and says so. Opsgenie incidents have no acknowledgement time; the resolution time is the incident’s last update once it is resolved or closed.

Jira Service Management operations

A dedicated Atlassian account with access to the operations schedules and Browse projects on the incident project, and an API token (id.atlassian.com → Security → API tokens). Incidents are Jira work items: give the JQL that selects them, such as project = OPS AND issuetype = Incident. Acknowledged is the first status change.

Known limits

• Schedules are read month by month and clipped to the period.
• Incidents are listed newest first; paging stops at the first incident created before the period.