Escalations without incidents

Sometimes you’ll find yourself needing someone to check on a situation, but it might not warrant an incident and a Slack channel.

You can now easily escalate to anyone in an organisation without creating an incident, straight from the dashboard, Slack, and the app. You might use this to investigate an alert before starting your full incident response workflow, or why not to get the attention of a coworker to come back to your booth at the conference?

You can escalate outside incidents with either incident.io On-call, or any of the paging providers we integrate with.

Creating an incident from an escalation

Incidents are important in your configuration as they allow you to group alerts together, and give you a place to triage problems. However, sometimes, you want a responder to assess an alert before creating an incident.

Previously, this required you to manually create an incident, where you’d lose the context of the alert. Now, you can declare an incident straight from an escalation, or connect the alert to an incident that’s already live from the same alert route. When you create an incident, we'll use the incident template from the route which the alert came in through.

Creating an incident from an escalation will only work through escalations that were created by an alert.

What else we’ve shipped

• 🆕 You can now filter for incidents which were opted out of the post-incident flow
• 🆕 You can now use alert priority in your alert route's grouping rules
• 💅 We'll automatically update your On-call status in the mobile app without you having to pull down to refresh
• 💅 URLs on alerts are now truncated for display in Slack, making it easier to read the welcome message when you come into an incident channel
• 💅 An escalation notification's urgency is now shown in the escalation message in the incident channel
• 💅 When creating overrides and cover requests in the mobile app, you'll no longer be able to choose an end time that's before the start time
• 💅 Improved our notifications UI so the drawer is smoother
• 💅 We fixed vertical alignment of condition badge on the Query Expression preview
• 💅 The 'Saved views' dropdown menu will now be scrollable when it overflows
• 💅 The 'Move to folder' on Workflows dropdown menu will now be scrollable when it overflows
• 💅 Display the minimised left sidebar correctly when on-call setup has not been completed
• 💅 Add additional context to follow-ups split by options to explain which options are available
• 🐛 Fixed a bug where we sometimes wouldn't let you provide a reason when declining an incident
• 🐛 Fixed a bug where our public schedules API wouldn't return entries for users that were scheduled through overrides and that were not on any of the schedule rotations
• 🐛 When clicking "no escalation path" from the schedule list to create a new path, we'll now set the associated schedule as the escalation target
• 🐛 Fixed a bug where we were not automatically refreshing catalog entries list when reordering the entries rank
• 🐛 We now show validation error when no values are selected when creating conditions with array values
• 🐛 We now show validation error when no If conditions are present when creating a condition rule
• 🐛 Fixed a bug syncing Slack channels state
• 🐛 Don't validate duration metrics on retrospective incidents
• 🐛 Allow users to update Atlassian status pages with maintenance impact
• 🐛 Show Slack channel selected for announcement rules even if it has been archived in Slack