The issue lifecycle: triage to verify
Triage, assign, action, resolve and verify — with comments, evidence and a full audit trail.
Rufineous Emmanuel
Last Update a day ago
Once an issue is raised (see Raising an issue), it moves through a controlled lifecycle — and every step is recorded in its Activity timeline.
The stages
Open an issue to see its actions:
- Triage — set the severity, priority, category and a due date. The issue advances from Reported to Triaged.
- Assign — pick who owns it (they're notified). Assigning doesn't change the status — it just gives it an owner.
- Mark in progress — work has started.
- Resolve — with a resolution note / repair evidence; the issue becomes Resolved.
- Verify — a second pair of eyes confirms the fix, moving it to Verified.
- Reopen — if it wasn't really fixed, back to Reported (the reopen count is tracked).
- Void — soft-remove something that shouldn't have been raised (kept for audit, hidden from the register). Deleting is permanent and manager-only.
Comments and evidence
- Comments — discuss the issue; the assignee and reporter are notified of new comments.
- Evidence — attach photos (before/after, the repair). Evidence added at raise time, during work, or by AI review all sits here.
- Work orders — where an asset repair is involved, the linked work order shows here too, and completing it can auto-resolve the issue.
A note on vehicle defects
Vehicle issues are graded and resolved through the Fleet module (the roadworthiness loop), not here — so on a vehicle issue you'll only see Assign and comments. See the Fleet articles for grading and taking a vehicle off-road.
Tip: use Verify as a genuine checkpoint on anything safety-related — "resolved" is one person's word that it's fixed; "verified" is a second person confirming it, and that distinction is exactly what an audit wants to see.