Context
Collection sites with many robots need a durable way to record operational incidents and shift handover context. Operators should not have to rely on chat history, handwritten notes, or raw logs to understand unresolved robot, network, storage, upload, or QA problems.
Scope
- Add an incident model with title, type, severity, status, owner, timestamps, description, and resolution fields.
- Link incidents to robots, workstations, tasks, batches, episodes, sync jobs, and alerts where applicable.
- Support incident lifecycle states such as open, investigating, mitigated, resolved, and closed.
- Add APIs for creating, updating, listing, and closing incidents.
- Generate shift handover summaries that include open incidents, recent critical events, unresolved QA or upload problems, and operational notes.
- Make incident counts visible in operations dashboards.
Acceptance Criteria
- Operators can create and update incidents linked to operational entities.
- Incident history preserves status changes, owner changes, and resolution notes.
- Shift handover API or report includes open incidents and recent high-priority events.
- Dashboard summaries include unresolved incident counts by severity.
- Tests cover incident creation, linking, status transitions, and handover summary generation.
Context
Collection sites with many robots need a durable way to record operational incidents and shift handover context. Operators should not have to rely on chat history, handwritten notes, or raw logs to understand unresolved robot, network, storage, upload, or QA problems.
Scope
Acceptance Criteria