Incidents · Guides
Follow up and write it up
An incident is over when it is resolved. Follow-ups and a write-up make sure the same one doesn't come back.
Add a follow-up
A follow-up is one thing to do because of the incident: “Alert when the card provider is slow”. Add it under Follow-ups on the incident's page, at any time, open or resolved:
- what is to be done, up to 200 characters;
- its owner, one of the project's people, or Nobody yet;
- the day it is due, today or later, or none.
Each follow-up then shows where it stands: Not done, Due today, Overdue once its day is over, or Done. Mark done and Not done switch it; Remove takes it off. The head of the list counts how many are done.
Track what is left
Follow-ups are easy to forget once the pressure is off. Incidents keeps them in sight:
- Follow-ups, in the project's sidebar, lists every one not done yet, the overdue first, each with its incident. Overdue shows those alone. Mark one done from there.
- The project's Overview counts the follow-ups open, with how many are overdue, and shows the first ones not done.
Write it up
Once an incident is resolved, its page has a Write-up with three parts, kept on the incident:
| Part | What goes in it |
|---|---|
| What happened | The story: when it began, each step, how long it took. Started from the timeline for you. |
| The cause | Why it happened. |
| What we change | What you do so it doesn't happen again. Each change worth tracking is a follow-up too. |
Write at least what happened, then Save the write-up. The page names who wrote it and when, and the timeline says it was written up. It can be changed later in the same place. Before an incident is resolved the write-up waits, and a declined incident has none.
Only your team reads it
What the timeline gives you
Beside the write-up, two lists help you tell the story right:
- From the timeline: each step it reached, when, and how much later than the one before, with how long it lasted in all.
- Just before it: what changed in the hour before it began, from Deploys, Flags, Secrets and Vulnerabilities when the project has them. A deploy or a flag turned on just before is the first suspect.
What happened starts as those facts in sentences, such as “It began 28.10.2026 09:07 EET; identified at 09:31 (24 min later), resolved at 09:48 (17 min later).” Edit it into the story.