Action items are Tasks or Follow-ups added as items to an incident timeline. Tasks should be completed during the incident to help resolve it.  Follow-ups are tasks to be completed post-incident, often providing team learning opportunities. These learnings can then be implemented in playbooks, training materials, or other resources for future incidents. Action items can be added manually through the web app or Slack, via API, from an Incident Role, or a Workflow during or after an incident. Markdown syntax is supported in your event description.

​
Examples:

  • “Add monitoring for API latency spikes.”
  • “Update the runbook for service X.”
  • “Conduct a game day for incident response training.”

​
Task

A task is something you do during the incident that helps move it forward, like troubleshooting. Create a task with:
  • Title (required)
  • Description
  • Who should be assigned?
  • When should the assignee be reminded?

​
Follow-up

A follow-up is completed after an incident has been resolved to prevent the issue from reoccurring, like refactoring a piece of code. Create a follow-up with:
  • Title (required)
  • Description
  • Priority
  • Who should be assigned?
  • Due date