Let's run a quick incident to check we've got everything wired up correctly.
There's a lot you can do with incident.io so we won't cover everything in depth, but you can read more about what's possible in our Getting Started guide.
<aside> 💡 In this guide we're running a fictional incident, but if you have a recent incident you can re-run using incident.io to see where and how it might have been able to help, even better!
</aside>
Create a incident with /incident Oh no!. For now we just want some basic incident automation so we won't put anything in the modal that pops up. Instead we'll just click "Submit".
This will do a number of things, including creating a new channel specific to this incident and making an internal incident homepage available. If we head into the incident channel, we'll see a few options presented to us right away.
You can do this with the quick action, or manually with /incident lead me (or /incident lead @person if you're not going to be leading the incident).
You can use the quick action on the initial incident message, or you can type /incident summary. Let's provide a quick insight into what's happening for the benefit of those who join the incident later. We'll see it reflected in the post in the announcement channel, on the incident homepage, and in our timeline, too.
Now we know a bit more about what's going on, let's rename the incident, which will give our channel a more descriptive name and update the title on the incident homepage.
Let's pretend this incident just heated up a little and adjust the severity. We'll see a bunch of things happen automatically, ensuring that the severity is reflected everywhere the incident is show.
Imagine we've got a good idea of what's causing the issue, let's progress the incident status to fixing with /incident status fixing.
Although we automatically note many events on your timeline, you can manually note them, too. Simply use Slack's "pinning"
Pinned messages in slack...
... will appear in the timeline