Issue Lifecycle
How an issue moves from Open to Closed — the status workflow, transition rules, and reinspection gates.
Issues follow a defined lifecycle with strict rules about who can transition status and when items can close. These rules ensure that all defects are properly resolved and verified. The lifecycle is the same for every category — a Safety issue closes the same way a Quality issue does.
Status Flow
Status Transitions
| From | To | Who Can Do It | How |
|---|---|---|---|
| Open | Assignee, creator, or project owner | Row menu → Start Fix | |
| In Progress | Fixed | Assignee, creator, or project owner | Row menu → Mark Fixed |
| Fixed | Closed | System (auto-close on reinspection) | Automatic when prerequisites met |
Key Rules
- The Performer can only FIX issues — they cannot close them directly
- Closure happens automatically when the Performer advances during reinspection AND all sibling issues are Fixed
- ALL sibling issues (from the same inspection) must be Fixed before any single issue can close
Closure Rules in Detail
Rule 1: Performer Cannot Close
The Performer (the inspector who created the verdicts that generated the issue) can mark items as Fixed but cannot close them. Closure requires verification through the reinspection workflow.
Rule 2: All Siblings Must Be Fixed
Issues from the same inspection are treated as a group ("siblings"). No individual issue can close until ALL siblings are Fixed or already Closed. This prevents partial resolution.
Example:
- Inspection "Pre-Pour Check" generates 3 issues: I-001, I-002, I-003
- I-001 is Fixed, I-002 is Fixed, I-003 is still In Progress
- None can close yet — I-003 must also reach Fixed status
Rule 3: Auto-Close on Reinspection
When the Performer has:
- Fixed all linked issues
- Re-inspected and recorded new verdicts on the previously failed items
- Submitted for review
The system automatically transitions all Fixed issues to Closed when the Performer advances the reinspection.
How the Interface Guides You
The app makes these prerequisites visible rather than silently blocking you.
Issue Detail Page
When an issue is Fixed and linked to a source inspection, a "Before you can close this issue" checklist block appears above the form content. It shows two ordered steps:
Step 1 — Fix all related issues Shows live progress (e.g., "2 of 3 fixed"). If siblings are still open or in progress, each one is listed as a clickable row — tap any to navigate directly to that issue without losing your place.
Step 2 — Complete the reinspection This step is dimmed until Step 1 is fully complete. Once all siblings are Fixed, an inline Perform Reinspection button appears inside the step so you can start the reinspection immediately.
When both steps are done, the checklist header changes to "Ready to close" and the footer's Close Issue button unlocks.
Footer button reflects current state
While prerequisites remain unmet, the Close Issue footer button shows a lock icon and is disabled — hover to see a tooltip with the specific reason. It never silently disappears; it stays visible so you always know what action comes next.
Issues Table (row actions)
When "Close Issue" is blocked in the row actions menu, it displays a lock icon instead of being grayed out, and hovering shows a tooltip. Clicking the item navigates you to the detail page where you can see and act on the prerequisites — it's never a dead-end no-op.
Reinspection Gate
If the "Require Issue Resolution Before Reinspection" policy is enabled:
| Condition | Can Reinspect? |
|---|---|
| All linked issues Fixed or Closed | ✅ Yes |
| Any linked issue is Open or In Progress | ❌ No — blocked |
The Performer sees a message explaining which issues need resolution before they can record reinspection verdicts.
Typical Lifecycle Example
Defect Identified
During inspection, the Performer marks "Rebar spacing" as Fail and toggles Auto-Create Issue ON. A Quality issue is created: "Rebar spacing — 180mm measured, 150mm required" → Status: Open.
Work Begins
The site team receives the issue. The assignee clicks Start Fix → Status: In Progress. Rework begins — rebar is repositioned to the correct spacing.
Fix Complete
After the rework, the assignee clicks Mark Fixed → Status: Fixed. All sibling issues from this inspection must also reach Fixed status.
Reinspection Verifies
The Performer re-inspects the items (reinspection cycle). When they submit for review with passing verdicts, the Fixed issues auto-transition to Closed.
Priority Impact
Priority doesn't affect the lifecycle mechanics but provides urgency signals:
| Priority | Typical Response |
|---|---|
| Critical | Immediate action — safety issues, stop-work items |
| High | Same-day response — blocking other trades or work |
| Medium | Standard rework timeline — 1-3 days |
| Low | Can be bundled with other work — cosmetic fixes |
Overdue items (past due date) show visual indicators in the table.
Next Steps
- Issues Overview — Table layout, categories, filtering, and management
- Reinspection — How the reinspection cycle works with issue resolution