Sub-issues
Break large issues into child issues with progress roll-up on the parent.
Sub-issues
Sub-issues (child issues) decompose large work into trackable pieces. Each child is a full issue with its own assignee, status, and estimate — the parent shows aggregate progress.
Create a sub-issue
Open the parent issue detail page.
In the Sub-issues section, click Add sub-issue (or use the create form embedded there).
Enter title and properties. The child inherits the parent's team by default.
Save. The parent list updates with completion counts.
You can also create sub-issues from issue templates that seed nested tasks — template rules may limit nesting depth.
Parent and child behavior
- Each sub-issue has its own workflow status and appears on team boards
- Completing sub-issues updates progress on the parent
- Sub-issues can have their own sub-issues when depth limits allow
- Filter issue lists to show or hide sub-issues — see Display options
Move to team
Sub-issues stay on the parent team unless you explicitly move them. Moving a parent does not automatically move children — review children after team changes.
Personal issues
Sub-issues require a team context in normal delivery flows. Personal top-level issues can later move to a team; create sub-issues after the parent belongs to a team.
API note
Child issues store a parent_id pointing to the parent issue. Clearing parent_id detaches the child without deleting it.
Next
- Create issues
- Edit issues
- Relations — dependencies between peers
Last updated on