Track duration metrics to keep on top of your incidents

Duration metrics

When reviewing an incident, it's useful to understand the timeline of events. For example, how long did it take to detect the issue? How long did it take to resolve the incident?

You can now configure duration metrics that you want to track using incident.io. Each metric is simply a relationship between two timestamps.

For example, you might want to track the time between when an incident is reported and when it's fixed as 'Time to fix'.

These metrics are then displayed on the incident homepage, to help put the incident into context.

You can also understand your duration data in more detail from our insights MTTX dashboard.

To start using duration metrics, go to Settings > Lifecycle to get started.

Jira child issues

We also shipped another much-requested feature this week. When syncing your incidents into a Jira project, you might have found it frustrating that there was no relation between the parent issue for the incident, and the child issues generated for each exported follow-up.

Now by default we'll create issues as children of the parent issue, so all the work for an incident is tracked neatly in Jira. How lovely.

🚀 What else we shipped

We had a big 'other stuff' week! The team shipped a whole bunch of things that people have been asking for, including:

• 🆕 Support setting a priority in PagerDuty escalation workflow steps
• 🆕 Use PagerDuty Priorities to set the severity of an auto-created incident
• 🆕 Support filtering by timestamp in insights
• 🆕 Allow folks to edit custom fields in the /incident update modal
• 🆕 Support exporting to Jira on private incidents, if an owner enables it
• 💅 Use official Slack URL picker
• 💅 Use official Slack number picker
• 💅 Use new Slack inputs for link & number custom fields, and for incident timestamps
• 💅 Turn custom fields modal into a whole page, to make it easier to edit
• 💅 Add a 'select all' button on the followups list page
• 💅 Show action and follow-up events on the timeline in a more compact format
• 💅 Notify the channel when someone resolves a PagerDuty incident
• 💅 Make follow-up statistics load faster
• 💅 Fix spacing & other consistency issues with Incidents page header
• 💅 Filter disabled PagerDuty services from escalation
• 💅 Add incident name to the recap modal
• 🐛 Make summary optional in the /inc rename modal
• 🐛 Actually expose external_issue_reference in the actions API
• 🐛 Made sure the Jira bookmark always appears in a new incident channel
• 🐛 Allow you to set incident timestamps when creating an incident via our API
• 🐛 Clean up policy violations when you delete a policy