Debriefs are a best practice and incredibly useful. Good debriefs rely on someone (you?) building a clear and cohesive timeline of the incident.

But it can become a real nightmare to retroactively parse through 100s of Slack messages, screenshots, Sentry errors, GitHub PRs/commits etc. to get a clear picture of what happened.

Not anymore! While your incident is playing out and you're focused on fixing, we'll be your scribe, hoovering up and digesting key events for you ⏱

You can find and incident's timeline within any incident.

There are 2 ways to add items to the timeline.

While in an incident's /inc-... channel, simply use the pin emoji (📌) on a message, screenshot etc. to add it to the timeline! 👇🏼

You can also use Slack's built-in "Pin to channel" command 👇🏼

There are some events that we'll note down automatically for you because they are best practice.

These include:

💡 Items pinned will be stamped at the time of their actual posting, not at the time at which they were pinned. So don't worry if you forgot to pin items in the heat of the moment! We'll make sure to position them adequately on the timeline.

Hiding items

You can show or hide events from your timeline with Edit mode. When hiding an event, it will no longer be visible for other users, and will be omitted from your autogenerated postmortem. These events can be re-shown at any point by using Edit mode.

Timeline notes

Notes can be added at specific points in your timeline to add descriptions of what was going on at that point. They will be exported as part of your post-mortem.

Commenting on the timeline

All timeline items, and timeline notes can be commented on. This is a great place to generate discussions about what happened during your incident.

Anyone can comment on timeline items, and you'll be able to see all comments throughout the timeline.