Skip to main content
Manage incident follow-ups. Incidents can have follow-ups associated with them, which track work that should be done after an incident (e.g. improving some documentation, or upgrading a dependency). They can also be exported to external issue trackers. You can manage follow-ups in the incident Slack channel with /incident follow-ups, or on the incident homepage.

The follow-up object

created_at
string<date-time>
required

When the follow-up was created

Example:

"2021-08-17T13:28:57.801578Z"

creator
object
required
Example:
id
string
required

Unique identifier for the follow-up

Example:

"01FCNDV6P870EA6S7TK1DSYDG0"

incident_id
string
required

Unique identifier of the incident the follow-up belongs to

Example:

"01FCNDV6P870EA6S7TK1DSYDG0"

labels
string[]
required

Labels associated with this follow-up

Example:
status
enum<string>
required

Status of the follow-up

Available options:
outstanding,
completed,
deleted,
not_doing
Example:

"outstanding"

title
string
required

Title of the follow-up

Example:

"Cat is stuck in the tree"

updated_at
string<date-time>
required

When the follow-up was last updated

Example:

"2021-08-17T13:28:57.801578Z"

assignee
object
Example:
assignee_team
object
Example:
completed_at
string<date-time>

When the follow-up was completed

Example:

"2021-08-17T13:28:57.801578Z"

description
string

Description of the follow-up

Example:

"Call the fire brigade"

external_issue_reference
object
Example:
priority
object
Example: