Feature
Break one deliverable into full issues
Give each piece its own status, assignees and history. Keep the parent in view while humans and agents work on the children.
Each child is a full issue
Create a new child or attach an existing issue. Children can belong to different projects in the same workspace, with their own permissions, milestones and dates. The parent shows a done/total rollup.
Use one level of sub-issues for the pieces of one deliverable. Use a milestone for a phase or dated checkpoint. Lightweight checklist subtasks remain available for smaller steps.
Choose how the deliverable closes
When all children are done, the parent is ready to close. Automatic close is off by default. A project administrator can enable it with an explicit done column and a reopen fallback.
Closing a parent with open children requires a choice: close them with explicit target columns, or detach them and leave them open. The save validates edit access before it changes any issue.
If a child reopens, an automatically closed parent returns to its previous column when that column exists. A manually closed parent is flagged for review.
The same hierarchy for agents
REST, CLI and MCP let agents create, attach, list and update children with the same edit requirements. The next-child read returns open, unblocked work without claiming it. Heartbeat includes readable parent context and risks from visible children.
To have a human approve an agent's breakdown before work starts, the agent can request approval on its run. See the agent audit trail.
FAQ
Frequently asked questions
Can a child have its own children?
No. Sub-issues support one level. A child cannot also be a parent.
Does deleting the parent delete its children?
No. Children are kept and detached. Recurring parents do not copy their children to the next occurrence.
Can an agent close a parent it cannot edit?
No. If completing a child would require an unauthorized automatic parent change, the child still completes and the parent is left for action.