Our main focus this week has been making sure it's easy to learn what incident.io is, and how it works. We've spent a lot of time working on great tooling for incident leads. However, by definition, there's only a single incident lead but many participants and observers. We want to make sure you have a great experience too!
As part of that, we've polished the messages that you get when joining an incident channel to make them clearer and more concise. Additionally, you can indicate whether you're there to help (we'll announce it in the channel if you are), there to observe, or if you want a quick introduction to incident.io.
We'll spend the rest of this week focusing on improvements to onboarding: look out for some new features coming out over the next few days!
What we shipped
- 🆕 Ever felt like your incident channel names didn't quite reflect who you were? I feel you. Well, incident channel name prefixes are now customisable: take your pick.
- 🆕 Want to write an update on your Statuspage without telling the world about it? You can now optionally set whether to deliver notifications to customers that have subscribed - previously, it was mandatory.
- 🆕 As part of our gradual but continual march to slash commands, we now support
call. Give it a try with
/incident lead me. Only a few left to go now..
- 🆕 Until this point, we didn't have a Statuspage. As a business that aims to make it easier to respond when things go wrong, that was an omission. You can now find us at status.incident.io. We, of course, will be using our Statuspage integration to update it.
- 🆕 We added lots of new customer logos to our homepage. Hello, new friends! 👋🏼
- 💅 Statuspage components now have their component group included in their name, if they have one.
- 💅 If you added an action and assigned it to a user using
/incident action, we'd send two separate updates into the channel. We've combined that into one update. Thanks for the feedback, Upvest!
- 💅 While we're on actions, we no longer post updates into the channel if you add new ones or update them after an incident is closed, keeping your channel history a little cleaner, once an incident is closed.
- 💅 The ID and name of the incident now appear in the browser title when viewing the incident homepage. Nice idea, Upvest and FACEIT! 🙏🏽
- 💅 When incident channels get archived, some features of the app aren't available. We used to tell you this, but not explain why. Now we do, avoiding a poor "computer says no" experience!
- 🐛 We used to return Statuspage component groups as a component that you could say was affected. That was a little
strange, so we don't do that anymore. Thanks to Bud for noticing this one!
- 🐛 If you
/incident summary Hello world, we used to discard
Hello world. That now forms part of the update that appears in the modal. Sorry about that.
- 🐛 In the document export of the timeline, pinned messages would appear at the timestamp that you pinned thme, not the timestamp that the message occured at. That was silly, and it's now fixed. Thanks FACEIT!
- 🐛 If you had more than 100 PagerDuty services, we'd error when you tried to escalate. We now perform typeahead search, so it's easier for you to find the service of interest.