Incident Timeline Template

Reconstruct an incident minute by minute, from detection to mitigation and resolution, for the post-incident review.

Sign in with your Edesy account, then click Use template in the preview to create the board, with its sample cards, in your workspace.

Category

Product & Software DevelopmentBug & Issue Tracking

Ideal for

Technology & StartupsEngineering & Product Teams

Columns

Detected → Investigating → Mitigating → Monitoring → Resolved

Sample cards

6

Custom fields

Severity, Environment

Request form

Creates cards in Detected

Columns and sample cards

The 5 columns of this board with its 6 sample cards, labels and fields, as they open in Edesy Boards. Copy the template to move cards and edit it.

  1. Detected

    2
    • 02:14 Pager alert: API latency > 5sPriority: highCritical
      Severity:
      S1 - Critical
      Environment:
      Production
    • 02:20 Status page updatedPriority: mediumCustomer impact
      Severity:
      S2 - Major
      Environment:
      Staging
      Checklist 0/5: Reproduce, Find root cause, Fix, Add test, Verify in staging
  2. Investigating

    1
    • 02:31 Identified runaway cron jobBackend
      Severity:
      S3 - Minor
      Environment:
      Development
  3. Mitigating

    1
    • 02:45 Job disabled, traffic recoveringPriority: lowBackend
      Severity:
      S4 - Trivial
      Environment:
      Production
  4. Monitoring

    1
    • 03:30 Metrics back to baselinePriority: urgent
      Severity:
      S1 - Critical
      Environment:
      Staging
      Checklist 3/3: Triage, Assign, Fix
  5. Resolved

    1 · done stage
    • Schedule post-incident reviewCustomer impact
      Severity:
      S2 - Major
      Environment:
      Development

Labels

Critical, Regression, UI, Backend, Won’t fix, Customer impact

Custom fields

Severity (Single select, on card), Environment (Single select, on card)

Request form: Report a bug · Incident Timeline

Tell us what you need; it lands on the “Detected” column of this board. Asks for Title, Description, Severity, Environment, Attachments; each submission becomes a card in Detected.

Card templates

Bug report

Incident Timeline Template: questions

Yes, through the board request form. Share its public link; each submission becomes a card in the chosen column, with the answers in the card fields. Viewers of a shared read-only board link can see the board without an account.

Yes. Board automations run when a card is created, moved, assigned, labelled, completed, due soon or overdue, when a form is submitted or on a schedule, and can move, assign, label or archive the card, add a checklist or comment, create another card, call a webhook or post to Slack.

Related templates