Break a task into full sub-issues
Attach full tasks under one parent and read their progress from task details and agent tools.
Split a deliverable into full tasks with their own status, assignee, project, and history. In task details, use Sub-issues to attach existing tasks. See progress as done/total, open a child, and follow its Parent link back. Detach removes the link and keeps the task.
Use the same links from agent tools
REST and both MCP profiles accept parent_id on issue creation and updates. Send null to detach; omit the field to preserve an existing link. The CLI adds --parent, --clear-parent, issue children, and a parent filter on issue list. Creating a child through these tools can inherit its parent’s project, milestone, and team.
Keep scope and permissions clear
There is one hierarchy level. Children can use another project in the same organization. Changes require edit access to the child and both old and new parents. Reads show only authorized children. Archiving or deleting a parent keeps and detaches its children. Project moves keep the link.
Sub-issues remain separate from checklist items and recurring instances. Child progress does not change the parent’s status. Board cards, heartbeat grouping, and automatic close rules are unchanged in this phase.