Insights usability improvements

Our customers love our Insights product, so we’ve spent some time to see how else we could enhance the experience. This week, we are releasing some improvements to Insights that should make everyone's lives a bit easier.

These new improvements will allow our customers to get access to the same reporting with less manual work.

Variable date aggregation

You can now dive deeper into your data with the ability to aggregate 'At a glance,' 'MTTX,' and 'Workload' by day, week, month, or quarter. This enhancement allows you to group your data to an aggregation that makes sense for your reporting time period.

For example, use monthly aggregation to check how specific incident severities contribute to changes in your quarterly incident count, helping you create targeted responses and better predict for future risks.

Split 'At a glance' by custom fields

The 'At a glance' dashboard now has a 'Split by custom fields' section. This will allow you to better compare the number of incidents based on different fields such as 'Feature' or 'Impacted team,' depending on your organisation's set up.

Additionally, analysing incidents split by severity levels and custom fields should help identify which incidents from which teams or features are trending upwards and may need additional support.

Period-over-period comparison

Discover the 'period-over-period' comparison table in 'At a glance' for incident creation. Dig into this month's or quarter's incident frequency against the previous period to pinpoint trends or plan for pre-emptive maintenance.

Simplified workflow deployment

We’ve made it easier to understand what will happen when you deploy a new workflow. You can now see your active incidents, and choose if your new workflow should run against those or not, if the conditions match. Your new workflow will always run against future incidents that match the conditions.

🚀 What else we've shipped

• 🆕 Enable you to deep-link to a specific follow-up (by copying the URL when editing a follow-up)
• 🆕 Add a new quick action for resolving an incident, which you can include in Settings → Slack Channels
• 🆕 You can now include ‘mode’ (i.e. test/tutorial/retrospective) when customizing the display info on the incident list view to easily identify certain kinds of incident
• 🆕 When updating custom fields in Slack, we’ll now make it clear when a field will be automatically derived
• 🆕 You can now choose for your retrospective incident to start in the post-incident flow, rather than in the closed state
• 🆕 You can now provide an update via /inc update at the same time as marking your incident as resolved
• 👷‍♂️ Improved our error-handling for the Linear integration, so we’ll be able to debug issues more quickly
• 💅 When declining an incident, show only the relevant fields in the Slack form
• 🐛 When selecting a Slack channel for a workflow or announcement rule to post in, the channel name will now always be kept up-to-date
• 🐛 No longer able to close an incident when required fields haven't yet loaded
• 🐛 Insights date filters updated to be more intuitive
• 🐛 We will now post the ‘you’ve merged incident A into B’ in the correct incident’s Slack channel
• 🐛 Improved our error-handling when setting up a customer status page, so it’s easier to understand why something isn’t working
• 🐛 When you delete an action from the web UI, we’ll now show that clearly on any recent Slack messages about that action
• 🐛 We'll now show an error when attempting to enable a Google Workspace integration with a service account that's already in use
• 🐛 We'll stop freezing when adding a related incident
• 🐛 We fixed a bug which was stopping us from being able to export some follow-ups to Jira
• 🐛 We've started sending updates to the channel for incidents in the post-incident flow
• 🐛 We fixed a bug which was letting users schedule a debrief in a placeholder that was already in use
• 🐛 We fixed a bug when syncing Slack users from Slack Enterprise Grid
• 🐛 We now handle linking a related incident that has already been suggested