What's up, doc?
We now have a number of customers using us daily to respond to incidents, and we're seeing more of you leaning into improving your post-incident followup. This is an area where until now we've been heavily opinionated, without much room for customisation - something we always knew we'd need to change.
We want to make it easy to imprint your process directly into incident.io - we want you and your team to feel like this is your tool, not someone else's.
We've always been able to automatically generate incident documents (also often referred to as post-mortems) and timelines automatically, but now you can now customise the format to your heart's content.
What we shipped
- 🆕 Assigning someone a role in an incident automatically invites them to the channel. Thanks for the polish suggestion, Upvest!
- 🆕 We added lots of new logos to our website. Hello WorkOS, Gitpod, Livestorm and Prolific!
- 💅 We added typeahead support to all places where you can select a user in Slack. This means we can support much larger organisations, and make it easier to search.
- 💅 We shortened the message that we send when an incident is closed. It was a little long and in-your-face.
- 💅 When creating an action in the dashboard, we now sort the list of users that you can assign the action to by name to make it far easier to scan. Thanks for the prod, Truelayer!
- 💅 We flipped the ordering of ratings when giving feedback so it goes lowest to highest, instead of the reverse. It felt more natural, you know?
- 💅 We now only show you a nudge to customise your roles if you haven't already done so. You're clearly an expert, so we don't need to waste your time with the basics.
- 💅 The incident lead/commander is now always shown first when interacting with roles in modals or settings. Because they're important like that.
- 👷🏽♀️ We totally finished our migration to slash commands. Conversational UI, be no more!
- 👷🏽♀️ We added company information to our receipts and invoices. We're growing up. Thanks for the prod, Upvest!
- 🐛 If you tried to close an incident twice, in some circumstances, we'd post two messages. We now handle this idempotently.
- 🐛 We found a particular edge case where changing the incident severity via a modal after an incident was closed would remove the
closed_at timestamp that we use for tracking. That was silly. It now doesn't do that. Thanks for helping us spot this one, Farewill!
- 🐛 We found a rare issue where we'd fetch the wrong message from Slack. This happens when we try and fetch a message that has been deleted. If it has, Slack will return the message immediately before the deleted message - which wasn't the message of interest. We've now fixed that! Sorry for the phantom bugs, Upvest and Bud!