Custom timeline events

Weekly Update

Custom timeline events

The timeline identifies the events that shaped an incident, allowing you to find insights and learnings by having a clear view of what went on.

But sometimes there might be important events which weren’t tracked by our system or in a Slack message. So we’re now letting you add custom events to the timeline! You might use these to document events like:

  • “Customer reported this as a problem”
  • “Service X was deployed”
  • “The team took a pizza break”

More shoutouts

Our customers have loved being able to give shoutouts to responders who did a particularly amazing job during a gnarly incident. We think it’s a great way to make people feel good about the work they’ve done, so we want to help you do more of them!

You can now add Give a shoutout as a post-incident task, which should help you pause and reflect on who deserves a notable mention before an incident is closed.

You can also now give a shoutout from the dashboard, using the three dots at the top right of the incident homepage.

Configure your suggested summaries

We recently released one of our features powered by AI, suggested summaries. These have seen huge traction, and ensure that summaries stay fresh with minimal effort.

We’ve now extended this feature so that you can decide which incident types you want to see suggested summaries for. For example, if you have an incident type which represents a product launch, migration or maintenance event, it might not make sense to have the summary structured into sections like Problem and Impact and so on.

Also, you can customise the names for each section from this modal! This might be handy if you prefer the term Triggers to Causes, for example.

You can configure both of these features in Settings > AI.

🚀 What else we’ve shipped

  • 🆕 Owner's can now be required when creating a follow-up
  • 🆕 We added the operation "does not contain one of" for strings in expressions
  • 🆕 There is now a search bar on the catalog allowing users to quickly find the catalog type they are looking for
  • 💅 We’ve made the navigate operation in query expressions run faster for large catalog types
  • 💅 We improved the error message if you don't choose an escalation policy when escalating
  • 💅 We now give a useful error message when you try to publish a private incident to an internal status page
  • 💅 We’ve made the assistant banner look cleaner on a small screen
  • 💅 We improved our 'lightning button' inputs so they look more consistent and ✨
  • 💅 We renamed "Export to Jira" with clearer language
  • 💅 We updated the copy within our Assistant feedback modal to be clearer
  • 💅 Links in Notion post-mortems are now hyperlinks
  • 💅 Custom Fields now have their own section in Notion post-mortems
  • 💅 You can now link bulk-exported JIRA follow-ups to their parent incident
  • 🐛 We fixed a bug where long custom field values blocked exports to Notion
  • 🐛 We fixed a bug where the trailing slash was missing when previewing status page URLs
  • 🐛 We fixed a bug where the 'add condition' popover would occasionally close before you'd finished writing the condition
  • 🐛 We now prevent the conditions popover from closing when selecting custom fields in expressions config
  • 🐛 We fixed a bug where derived custom field values wouldn't be saved from the web UI in some situations
  • 🐛 We fixed a bug preventing role assignment in the post-incident flow
  • 🐛 We fixed a bug preventing bulk editing actions
  • 🐛 We fixed a bug where you couldn't create a timestamp with a set by rule
  • 🐛 We fixed a bug where localizeJS wouldn't load on sub pages if you viewed multiple sub pages in a row

Operational excellence starts here