- Reboot that server
- Send some comms to an affected customer
- Improve test coverage of a given codepath
- Share the debrief document with all affected customers
How do I create follow-ups?
There are three ways you can do this:- React with the
:fast_forward:emoji to any Slack message within the incident channel


- Use the command /inc follow-up, to create new follow-ups and post any open follow-ups within the channel

- Create the follow-up directly in your issue tracker, and paste a link into the Slack channel

- Import an existing ticket from your issue tracker as a follow-up, from the incident homepage in the dashboard
What can I do with follow-ups?
Editing follow-ups
If a follow-up is exported to an external issue tracker like Jira, we’ll listen for changes and keep the follow-up in line on our side. The tracker then owns the title, description, status, owner and labels, so that’s where you edit them. See issue tracker sync for the trackers we support and exactly which fields sync in which direction. If it isn’t exported, you can manage it via Slack (using/inc follow-ups) or via the incident homepage from the Follow-ups tab.
You can also assign a Priority to a follow-up, to help drive Policies and communicate the difference between follow-ups. You can read more about Follow-up Priorities.
You can assign follow-ups to a Team as well as an individual user, which is useful when you know which team owns the work but not yet who will do it. Follow-ups can also be tagged with Labels, which can be used for filtering, and which sync in from your issue tracker once a follow-up is exported to it.
Tracking follow-ups
You can track follow-ups from the Follow-ups page in the web dashboard. This allows you to see the status of follow-ups across all your incidents, as well as take actions such as sending reminders and bulk-editing follow-ups.