Issue lifecycle — open, in-progress, resolved
An Issue moves through three states: open → in progress → resolved. Severity is low / medium / high / critical. There is no 'Closed' state — resolved is the terminal state.
Issues live on Mission Control's Open observations tile, the Maintenance tab, the Vessel Briefing, and any observation drawer where they were promoted. You change the status from the observation's drawer — the Status picker (Open, Working, Resolved) — and choosing Resolved asks how it was resolved (below).
Steps
-
Three states only
Open (just logged), In progress (someone is working it), Resolved (done). There is no separate 'Closed' state.
The drawer's own picker labels the middle one WORKING; the list rows say 'In progress'. Same state, two words for it.
Resolving does not simply ask for a note — see 'How it was resolved' below.
-
Urgency is the field you actually pick
Five tiers, and they are what the Log Observation sheet asks for: COSMETIC (looks bad, affects nothing), WEAR (working, but on its way out), NEEDS ATTENTION, URGENT, SAFETY. Each carries a one-line description on the sheet so you can tell them apart.
The Maintenance list sorts on urgency, then category, then newest. It does not consult severity at all.
Severity — Low, Medium, High, Critical — still exists underneath and is derived from your urgency automatically; Ready-Now uses critical and high as its blocking set. You never set it by hand.
-
Promote an observation to an issue
From an Observation Drawer or from the Vessel Briefing observation list, swipe or open the context menu and tap 'Promote to Issue'.
-
How it was resolved — and why the answer matters
Resolving asks HOW, not just whether. Eight outcomes:
- Fixed — verified
- Fixed — not re-tested
- Worked around (note required)
- Not reproducible
and, under More:
- Deferred (note required)
- Vendor declined
- Design-inherent (note required)
- Captain accepted (note required)
Where a note is required the Resolve button stays disabled until you type one. There is also 'Just mark resolved — no details' if you would rather not say.
THE OUTCOME IS NOT JUST BOOKKEEPING. Only the two FIXED outcomes count as genuinely resolved; worked around, deferred, declined, design-inherent and captain-accepted all close the row while telling the boat's memory that the problem was never actually cured — which is exactly what you want it to know when the same fault comes back. Picking 'Worked around' for something you properly fixed puts the wrong outcome on the record, and picking 'Fixed — verified' for a bodge puts a worse one there; a later match shows that outcome back to you.