Issues
The Issues view is a workflow-driven tracker for live issues during an event — separate from the Jobs board (kanban) covered in Jobs and Issues. Where a Job is a task ticket, an Issue is a fault report: tyre puncture, electrical glitch, gearbox jolt, fuel-flow drift.
Find it at Event → Issues in the ribbon. Route:
/events/:eventId/issues.
What an Issue carries
| Field | Notes |
|---|---|
title | One-line summary |
description | Free-text |
severity | critical / major / minor / info |
category | Free-form tag (mechanical, electrical, aero, tyre, data, …) |
state | The issue's position in the workflow (e.g. open, acknowledged, in_progress, resolved, closed) |
assignee | Optional membership reference |
acknowledgedAt | Timestamp set by POST /issues/:id/acknowledge |
resolvedAt | Timestamp set by POST /issues/:id/resolve |
Workflow-driven
Each issue is bound to an Issue Workflow (a state-machine spec authored in Admin → Issue Workflows). The workflow declares:
- The list of states
- Which transitions are legal from each state
- Whether a transition requires a reason / comment
The Issues screen surfaces only the legal transitions for the current state — you can't accidentally move an issue into an illegal state.
The two convenience actions are first-class endpoints:
POST /issues/:id/acknowledge— flag the issue as seen by an engineerPOST /issues/:id/resolve— flag the issue as resolved (resolves all transitions to the workflow's terminal state)
What you can do today
- Full CRUD via
/issues - Apply a workflow per issue
- Acknowledge / resolve via the convenience endpoints
- Filter by severity / state / assignee
- Author a workflow tailored to your team's process
What's coming
- Real-time multi-user state changes (today: REST only, no WebSocket push)
- Cross-event Global Issue List — issues that persist across events
- Auto-attach an issue when a lap KPI breaches a threshold
- iPad-optimised "report new issue" flow for mechanics
- Notification routing via webhooks (the
/webhooksplumbing is in place; the issue → webhook event publisher is queued)