Auto-Export Incidents as Jira Tickets

Weekly Update

Auto-Export Incidents to Jira Cloud

We have expanded the capabilities of Jira Cloud integration 💪

Now, when you auto-export incidents as Jira tickets, you can configure the fields we send. We'll then keep the ticket up-to-date as the incident progresses.

Using the same functionality as Workflows, you are able to configure the conditions an incident must meet before it is auto-exported to Jira. An example set of conditions is: auto-export to Jira when an incident has a severity of at least Major and is a Security incident.

A screenshot of Configuring Conditions for Auto-Exporting to Jira

Once the Jira ticket is created, fields of the ticket will be kept in sync as incident updates occur. The fields can be set to be a constant value or a variable. For example, the "Assignee" field can be always be set to Bob (constant), or the Incident Lead (variable). If you choose Incident Lead, when someone is set as the Incident Lead during an incident, the assignee of the Jira ticket will be set to that user.

A screenshot of Configuring Jira Cloud ticket assignee

Additionally, when a user sends an incident update, a comment of the update will be posted under the auto-exported Jira ticket.

A screenshot of incident update under Jira ticket

Connecting to Jira Cloud is easy, just navigate to Settings -> Integrations. Click on Connect/Configure for Jira and follow the instructions.

What else we shipped

  • 💅 Add a link to the incident.io incident when you connect a PagerDuty incident
  • 🐛 Fix default workflow template for sending an email