Summary templates

Summary templates can be used to encourage responders to provide relevant and consistent information across all of your incidents. This further helps to reduce the cognitive load on responders and lowers the barrier for newcomers to respond to incidents.

They can be defined for each individual incident type, as types such as “Operations” and “Security” are likely to have very different defaults.

You can go to Settings → Incident Types → Summary template to set this up now.

Customizable names for debrief

The terminology for postmortems and debriefs isn’t yet standardized across the industry. We’ve optimized for familiarity by using the most standard terminology, but we know that others prefer different terms to best describe them.

If you use a different word to represent a debrief meeting, you can now change the default. We'll then use your preferred name across our entire platform. Additionally, you can configure the default title and description we use when pre-filling a debrief event.

This is now available in Settings → Debriefs → Customise debrief name.

Additional polish for workflows, conditions, variables and expressions

We recently released a new look for workflows, for a much more intuitive experience. We have now rolled out these improvements across the rest of our platform. Some of the highlights from these improvements are:

• When you use an expression in a workflow step, we now show you the whole expression in the sidebar instead of just the name, so you can understand your steps more easily
• We also show this fancy new expressions view in other contexts, such as policies
• Whenever you’re inserting variables or adding conditions, you’ll get the same new ‘popover’ experience - keeping things smooth
• When rich text is being edited, we use our new and improved styling

Catalog colors and icons

We’ve swapped out red and gray for pink and cyan, and added orange alongside a few extra icons. This prevents any confusion, as red could be mistakenly interpreted as broken and grey interpreted as inactive.

Exposing Jira problems

We now expose any errors that have been encountered when creating a Jira issue for an incident. This makes it clear why that failure has happened, as well as a pointer as to how it happened. This gives you more observability and control, reducing confusion, and improving the time to fix any problems.

🚀 What else we shipped