It can be useful to categorise or track dimensions against incidents, such as which teams were involved, what systems were affected, or how many customers were impacted.
incident.io provides Custom Fields to help tag incidents with this data.
Creating fields
Before you can use Custom Fields, you have to tell incident.io which fields you want to track.
You can do this in your Settings page, where you can control what fields we'll collect, along with when and if responders would be required to provide the field.
Think carefully about being overly restrictive- if you require a field when opening an incident, responders will be forced to provide a value before they begin responding. Only require what you absolutely must, and prefer requiring at incident close than at incident start.
Setting fields on incident create
If you require setting a field when creating an incident, responders will be asked to provide the value when they first open an incident:
Setting fields during an incident
At any point during an incident, you can use the /incident fields command to open a Slack modal that shows all configured custom fields.
