wr-itil:manage-incident

You can manage the entire incident lifecycle by declaring, triaging, mitigating, and closing incidents using a structured workflow. This approach enforces documenting observations, hypotheses, and mitigation attempts to restore service quickly.

An evidence-first incident management approach requires documenting observations, forming hypotheses with supporting evidence, and recording mitigation attempts. This structured workflow ensures service restoration is driven by verified facts rather than assumptions.

Once service is restored, you can link the incident and automatically hand off to a manage-problem workflow for persistent root-cause analysis. This ensures incidents are properly migrated for deeper investigation after mitigation.

Yes, you can update incidents and track mitigation attempts throughout the response process. The structured incident document supports adding observations and hypotheses with evidence to evaluate each mitigation step effectively.

You should close an incident once service restoration is confirmed and documented. The evidence-first workflow requires capturing observations and mitigation attempts before closing, ensuring the incident lifecycle is fully resolved before handoff.

Yes, the incident management workflow supports listing active incidents alongside declaring, updating, and mitigating them. You can track the end-to-end lifecycle of IT operations incidents from declaration through closure.