IT system outages in companies are not only annoying, they also cause costs and extra work. The Statuspage service developed by Atlassian provides an overview: which systems are affected by an outage, how severe is the outage, and what is the status of an outage. The drawback: IT administrators have to manually enter and maintain the respective outages in Statuspage. Here, an extension developed by catworkx provides a remedy: by connecting Jira Software to Statuspage, it is possible to document and control outages directly from within Jira.

Central control of IT outages: catworkx creates a connection between Jira and Statuspage
The project at a glance
Industry
Financial Service Providers
Requirements
Incidents should be reported to Statuspage via Jira.
Solution
- Jira Software
- Statuspage (Atlassian)
- Development of a trigger function from Jira (catworkx)
Benefits
- Central control of incidents via Jira
- Transparency in incidents
- Assignment of incidents to their respective components
The transparency of IT applications strengthens the trust of customers and employees in companies. This is precisely what the Atlassian service Statuspage stands for, making potential outages (incidents) of IT systems comprehensible. A nationwide German financial service provider had been using Statuspage for its customers and employees for some time to inform them about current IT system outages or maintenance work. The status of, for example, apps, the webshop, or the email server can be queried at any time clearly on one page. Although Statuspage has numerous interfaces to third-party cloud applications, there is also an app that connects Statuspage with Jira Service Management (JSM) – but a notification from Jira Software was not possible until now.

This was precisely the requirement of the financial service provider, who approached catworkx with this issue. The goal was to automatically generate incidents recorded as issues in Jira as notifications in Statuspage. The financial service provider already used its own Jira system for monitoring its IT systems. The solution developed by the catworkx Development Team now makes it possible to generate an "Incident" in Statuspage through a "Create Issue" in Jira. The Statuspage components affected by the incident (e.g., apps, webshop, or email server) are selected via a "Multiselect List" in Jira Software. This list is maintained by a Jira administrator and contains the exact component names that also correspond to the components in Statuspage. Furthermore, a template is selected in Jira via a "Select List" – here too, the template names must be the same in Jira and Statuspage. The template selection sets an incident status (e.g., Operational, Total Outage, or Partial Outage).
Core Requirement
A crucial requirement was that the following characteristics could be recorded for each incident: What is the impact of the outage? Here, three levels are defined: High, Medium, or Low. Furthermore, it should be specified which components are affected and what the working status of an incident is: "New," "Investigating," or "Resolved."
The advantage of the connection between Jira Software and Statuspage developed by catworkx is that outage notifications for all affected IT systems can be centrally controlled by a Jira administrator. This saves multiple inquiries from employees or customers who notice a disruption in the IT systems. Furthermore, this solution can be expanded with additional functions. For example, with further development, it is possible for status changes of an incident – for example, from "Investigating" to "Resolved" – to be maintained directly in Jira. This makes it possible to control the processing of incidents using Jira.
Contact Us!
We advise you on the entire Atlassian Ecosystem and are happy to support you in optimizing license models and costs.