Incident lifecycle
Every incident in Batida progresses through four statuses. Each transition is recorded in the timeline with a timestamp and the acting user.
Status flow
Investigating → Identified → Monitoring → Resolved
Transitions move forward only. You cannot move an incident back to a previous status. If a resolved incident flares up again, create a new incident and link it to the original.
Status definitions
Investigating
The incident has been created and the team is gathering information. The goal is to understand the scope, impact, and potential root cause. During this phase the Commander should be assigned and initial responders notified.
Who can set: any team member (this is the default status on creation).
Identified
The team has determined the root cause or at least identified the affected system. A fix or workaround is being developed. The Commander should communicate an ETA to stakeholders.
Who can set: Commander or any Responder assigned to the incident.
Monitoring
The fix has been applied and the team is watching the system to confirm stability. No new issues should appear. If the problem recurs, you may need to return to investigation by creating a follow-up incident.
Who can set: Commander or any Responder assigned to the incident.
Resolved
The incident is fully addressed. Systems are stable, stakeholders have been informed, and the incident can be closed. Once resolved, Batida triggers the feedback collection flow.
Who can set: Commander only. This restriction ensures that the person leading the response confirms resolution before the incident is closed.
Role-based restrictions
| Status | Commander | Responder | Unassigned member |
|---|---|---|---|
| Investigating | yes | yes | yes |
| Identified | yes | yes | no |
| Monitoring | yes | yes | no |
| Resolved | yes | no | no |
Auto-transition rules
Batida can automatically transition incidents based on rules configured by your admin:
- Auto-resolve -- if no activity is logged for a configurable period after reaching Monitoring, the incident is automatically moved to Resolved.
- SLA breach escalation -- if an incident exceeds its SLA target for the current status, the Commander and all Responders receive an escalation notification.
See also
- Severity levels -- SLA targets per severity.
- Assigning commanders -- how Commanders are designated.
- Timeline & activity log -- tracking status changes over time.