Back to Changelog
Back to Changelog

July 20, 2023

Others

Incident Triage: Investigate Potential Incidents Faster

Incident Triage: Investigate Potential Incidents Faster

🚑 Incident Triage: Investigate Potential Incidents Faster

Start tracking potential incidents as soon as they develop, without the pressures of kicking off all the processes that come with declaring an incident. When you use the “In Triage” feature, we’ll create a triage incident while you investigate and get the right people in the room. From there, you can choose to update the incident status to “started” to declare an active incident, or “canceled” to track how the problem was resolved and close it.

Some benefits of incorporating triage status into your incident management:

  • Capture incident data sooner
  • Avoid duplicate efforts due to lack of visibility
  • Reduce on-call fatigue from false alarms
  • Create a greater sense of psychological safety around starting incidents

To get started with triage incidents, head into Configuration settings from your main menu in the web platform and navigate to “Forms & Custom Fields”. Click “Configure” for the form you want to add Triage to (this will typically be your “New incident” form to start out with), and add the “Mark as In Triage” field. With this field added, you’ll be able to create triage incidents in Slack or in the web platform just like any other incident, by simply toggling the “In Triage” option in the form when the incident is created.

Triage also supports its own set of workflows, so you can determine exactly what you want to happen when a triage incident is started. When creating custom workflows, you’ll find “In Triage” in the status options.

Check out a quick video demo of triage in action below and learn more about the benefits of this feature in our latest blog post.


🌝 New & Improved

🆕 Introduced Auto-Assign Role from On-Call Rotation and Invite On-Call to Slack Channel capabilities for VictorOps integration
🆕 Custom boolean fields can now be created with independent Name and Description fields
💅 Enabled liquid variables containing URLs to be clickable links in retrospectives created in Google Doc
💅 Up-versioned Terraform to v1.0.7 with a lot of improvements and fixed. See our Changelog.
🐛 Fixed the Page VictorOps On-Call task to allow paging via escalation policy or user
🐛 Fixed broken link on Integrations page for Statuspage.io docs

Previous post
Previous post
You are viewing the latest post

🚨 New Alert Sources: Azure, CloudWatch, and Google Cloud

☎️ Live Call Routing

🤑 On-Call Pay Calculator

💓 Heartbeats: Continuous System Monitoring

🚨 Alert Grouping

🤓 Smart Defaults for Google Meet & Zoom

🧼 Redesigned Incident Announcement & Update Slack Blocks

💅 New Navigation Bar and Configuration UI

🥸 Sync On-Call Schedules with Slack User Groups

🕵️‍♀️ /rootly lookup: Find and Filter Recent Incidents in Slack

👯‍♀️ On-Call Shadowing

🔌 Generic Webhook Alert Source

🔒 Lock Individual Workflows

🐦‍⬛ Round Robin Escalation Policies

🚨 Alert Sources

🔔 Configurable On-Call Shift Reminders

🪄 Dynamic Forms

🔐 Granular Role-Based Access Control Settings for On-Call

✉️ Emails as an On-Call Alert Source

🗓️ View Multiple On-Call Schedules Together

🤝 Partial Shift Overrides in Rootly On-Call

🏗️ Terraform + API Support for Rootly On-Call

🦉 Rootly x Thena Integration

🎬 New Full Platform Tour on Rootly.com

🔦 Drop-down Search in Escalation Policy Builder