Linear Issue Hierarchy
Large tasks hide risk. A single issue called "Build the settings page" can sit in progress for weeks with no visible signal. Linear solves this with parent issues and sub-issues. A parent describes the big goal, and sub-issues describe the small steps.
Parent and Sub-Issue Basics
A sub-issue is a normal issue attached to a parent. It keeps its own title, assignee, status, priority, and estimate. The parent shows a progress indicator that updates as sub-issues close.
ENG-200 Build settings page (Parent) │ ├── ENG-201 Design form layout Done ├── ENG-202 Build profile tab In Progress ├── ENG-203 Build billing tab Todo └── ENG-204 Write tests Todo Parent progress: 1 of 4 complete
Everyday Comparison
Cooking a family dinner shows the idea well. "Cook dinner" is the parent. Chopping vegetables, boiling rice, and setting the table are the sub-issues. Different family members can handle different steps at the same time, and the dinner is ready when every step is done.
Create a Sub-Issue
- Open the parent issue.
- Click Add sub-issues below the description.
- Type a title and press Enter.
- Repeat for each step.
Existing issues can become sub-issues too. Open the issue, use the issue menu, and choose to set a parent issue. Linear links the two issues right away.
Assign Work Across People
Each sub-issue takes a separate assignee. A designer can own the layout step while a developer owns the build step. The parent stays with the person who guards the overall result.
Automatic Parent Closing
Team settings include options that close a parent issue after all sub-issues finish. Turn on this option if you want completion to flow upward without manual clicks. Leave it off if a parent needs a final review step.
When to Use Each Structure
| Situation | Best Structure | Reason |
|---|---|---|
| Work takes more than a week | Parent with sub-issues | Smaller pieces show progress |
| Several people share one goal | Parent with sub-issues | Each person owns one step |
| Steps are tiny and done by one person | Checklist in the description | Avoids clutter in the issue list |
| Work spans many weeks and teams | Project | Projects hold dates and updates |
Sizing Guidelines
Right-Sized Sub-Issues
Aim for sub-issues that one person finishes in one to three days. Anything shorter belongs in a checklist. Anything longer needs another split.
Depth Limits
Linear allows sub-issues under sub-issues. Stay within two levels for most work. Deep trees confuse readers and slow down planning.
Clear Titles
Start each title with a verb. "Build billing tab" tells a reader the action, while "Billing" leaves the reader guessing.
Common Mistakes
- Creating sub-issues for every tiny action. The issue list turns noisy.
- Leaving the parent without a description. Readers lose the purpose of the group.
- Moving sub-issues into cycles while leaving the parent behind. Keep related work in the same cycle when possible.
Plan Cycles With Sub-Issues
Sub-issues improve cycle planning. Teams can pull individual steps into a cycle without committing the whole parent. A parent that spans three cycles shows progress in each one. Planners spot unassigned steps quickly.
Review Progress at the Parent Level
Managers read parent issues to judge large pieces of work. Engineers read sub-issues to find their next task. Both groups work from one structure, so reports match daily reality.
Reorganize When Plans Change
Requirements shift. Move a sub-issue to another parent, promote it to a standalone issue, or cancel it. Keep the tree current so it reflects the actual plan.