Skip to content
Fulstech Docs

Use Case: Incident Follow-up

Use this when: the incident already exists, but follow-up work repeats.

Example

Section titled “Example”
INC-123 — Checkout outage
├─ Complete root-cause analysis
├─ Review alerting gaps
├─ Define corrective actions
└─ Prepare incident retrospective

Best fit

Section titled “Best fit”

Apply to the existing incident

A second Apply preview shows Keep decisions and one selected follow-up subtask

This is a second preview after an earlier Apply run. The root fields show Keep and one follow-up child is selected; Apply changes was not selected a second time. The four-item outline above is a possible expanded incident process, not the photographed fixture.

What this gives the team

Section titled “What this gives the team”
  • The existing incident remains the source of truth.
  • Standard follow-up work is added only after review.
  • Partial child creation can resume from the same run.

Preview Current vs Proposed, keep the real incident details, and add only the follow-up work you need.

Also works for

Section titled “Also works for”

Security events · failed deployments · customer escalations · defect reviews · operational exceptions.

Build the follow-up template →
Use Apply →