The tracker needs master issues that group sub-issues, starting with the Visit Flanders dashboard story (#589 with subs #590 to #597).
SCOPE (implemented in v1.13.0)
- Issue gets an optional parent field. Summaries carry it so clients can group sub-issues.
- Validation: the parent must exist, an issue cannot be its own parent, and a parent chain cannot form a cycle. Invalid values return 400.
- API: parent on POST /api/v1/issues; PATCH /api/v1/issues/{id} sets (N), clears (0), or leaves unchanged (absent).
- Public /report form: optional parent field with ?parent= prefill.
- Web: parent link on the issue pages, sub-issue list with status badges on the parent page, admin sidebar control at POST /admin/issues/{id}/parent.
- YAML store needs no migration: old files unmarshal with parent 0.
- Runbook: parent section added, stale pre-containerization infrastructure section replaced with the scale deployment. Testbook docs/testbooks/parent-issues.md added.
DONE WHEN
v1.13.0 runs as the hydraissue scale on pi-node-004-nvme and #590 shows Parent: #589 on the live site.
Implemented in hydraissue v1.13.0 (commit a28ecf2, testbook docs/testbooks/parent-issues.md). Deployed to the hydraissue scale on pi-node-004-nvme via hydraskin update (12s rebuild, health verified). Live check: #589 shows its 8 sub-issues, #590 shows Parent: #589. Note: the scaleregistry push token was rotated 2026-08-28 07:29 UTC; the hydraissue repo secret and the node auth files (/etc/hydraskin/registry-auth.json and /run/containers/0/auth.json on pi-node-004-nvme) were refreshed to unblock this release. Other repos and nodes still carry the old token.