Observation vs. Issue — what's the difference?
Same tab, two intents. Use the right one.
theONE's Maintenance tab handles two related concepts. They share a model and a list but they mean different things. Picking the right one keeps your blocker badge count honest.
Steps
-
Observation = something you noticed
Walking the boat, you spot teak that's drying out, anode wear, a screw working loose. Log it as an Observation. It records the system, the location on the boat, an urgency (cosmetic / wear / needs attention / urgent / safety), and optional photos. It does NOT count as a blocker by default.
-
Issue = something blocking
An issue is a problem that's blocking a trip, a playbook, or a system. The starboard engine won't start. The watermaker is alarming. Log it as an Issue (or let a Playbook auto-create one). Issues default to counting as blockers on Mission Control.
-
Same tab, same model
Both live in the Maintenance tab. The list is filterable. The 5-tier urgency ladder is the same. Photos, location, system — all the same fields. The two differ only in whether they count toward your blocker badge.
-
When in doubt, log as Observation
It's easier to upgrade an Observation to an Issue (open the drawer → toggle 'Count toward blockers') than to create then delete. Observations are the safer default for anything you notice while not actively troubleshooting.