We added new ways for you and your team to collaborate to resolve issues.
Status selector in incidents
Not all test and monitor failures have the same level of severity. Some may not be issues at all.
We’re giving you the option to select the status of each individual failure.
For example, if you are looking at something, you can mark it as Investigating. Everyone in your team will see when you started looking at it.
You can also mark failures as No action needed or as Fixed.
This will streamline the incident management workflow, reducing back and forth in Slack and keeping things tidy for your team.
Comments in incidents
Slack threads are great for quick back-and-forths, but they can miss a lot of context.
We’re introducing comments on incidents and issues where you and your team can have conversations with the full context.
These comments remain saved after the incident is closed, helping you remember information about what failed and how you solved it.
Related ongoing incidents in the product’s dashboard
When an ongoing incident is affecting a product, it is clear in the dashboard and the product overview.
This provides visibility into how declared incidents affect different parts of your stack.
All issues history view
A history of issues is essential to understanding what failed in the past.
We are introducing a section that lists current and past issues, including their duration and affected assets.
