Choose parent and sub-issue close rules
Explicit manual close decisions, optional automatic parent close and reopen, and hierarchy webhook payloads.
A parent with open sub-issues now requires an explicit close decision. Close its open children using a selected done target for each child project, or detach the open children and leave their status unchanged. The save checks edit access for every issue that changes and rejects invalid choices together.
Automatic parent close is off by default. Project administrators can enable it by selecting a done column and a not-done reopen fallback. When the last child finishes, an authorized parent change closes the parent. Reopening a child restores an automatically closed parent to its previous column when it still exists, or to the configured fallback. A manually closed parent stays closed and is flagged for review. Lack of parent edit access does not prevent the child from completing.
REST, CLI and full/public MCP expose the same decisions and project policy. Issue subscription payloads include hierarchy and rollup fields; the new issue.ready_to_close event lets receivers react to parent readiness. Existing delivery signatures, retries and deduplication still apply.
Sub-issues remain one level deep, can span projects in one workspace, and stay separate from checklist subtasks and recurrence lineage. Recurring parents do not copy child issues to the next occurrence.