Parent and Sub-Issues
Use sub-issues to break down larger "parent" tasks into smaller pieces of work.
Sub-issues are a good option when a set of work is too large to be its own issue but too small to be a project. It's also ideal for splitting up work shared across teammates, since we limit issues to one assignee.
We treat sub-issues and their parent issues as as separate entities. A sub-issue is related to it's parent hierarchy but they do not share properties and do not sum up or aggregate properties. A sub-issue has it's own own estimate count, assignee, labels, team, etc that is unrelated to the parent issue and vice versa.
If you use parent issues to summarize work but not represent tasks, you can configure estimates in team settings to allow for zero estimates, then assign a zero point value to parent issues.
Cmd/Ctrl Shift O to create sub-issue and Esc to exit sub-issue editor
Cmd/Ctrl Shift Pto add a parent
Cmd/CtrlShift Down to create sub-issue
CmdK Set parent issue via the command line
Create sub-issues directly by opening the parent issue and then clicking the
+ Add sub-issues button below the issue description. This will launch the launch the sub-issue editor. You can also use the shortcut Command Shift O to open the editor.
When you save a sub-issue, it will automatically launch the editor to create a new one. If you want to create a new one with the same values (labels/assignee etc.) you can press Command Shift Enter or Shift+click the save button.
Press Esc to exit the sub-issue editor and continue updating the parent issue.
You can turn a comment under an Issue into a sub-issue by hovering over a comment and clicking the ... menu then "new sub-issue from comment".
Selecting a comments text and pressing Command Shift O will also create a sub-issue.
If you have a checklist, you can highlight the checklist and hit Command Shift O to convert to sub-issues.
You can add a template using the templates icon when creating a sub-issue or using the command menu under "Create new sub-issue from template" when viewing the Parent.
Sub-issues created in the editor automatically copy issue properties from the parent issue such as the project and cycle as long as those are set before you create the sub-issue.
Team, labels and assignees are not copied over. You can't create sub-issues while editing the parent issue but the option will come up once you press save.
You can duplicate a parent and it's sub-issues from the Parent's ...menu under "Duplicate" and hit the toggle "Include sub-issues".
Turn an existing issue(s) into sub-issues of another issue by selecting one or multiple issues and then taking the action to set the parent issue, accessible from the command menu and if you right-click over the issues.
To make an existing issue a parent issue of another issue, hover over a sub-issue and take the action "Set Parent" in the contextual menu, command menu or
Turn the sub-issues into a project by hovering over the Parent's
∙∙∙ menu and choosing "Convert to project."
Update a sub-issue to edit it just like you would any other issue. You can make changes to the sub-issue from a list or board view or open it to edit.
To make changes to a sub-issue while viewing the parent issue, hover over the issue in the sub-issue list and then use a keyboard shortcut or right-click to open a contextual menu to update any issue field. Some issue fields will show up by default on the issue, such as assignee and team, and you can click to update those.
We also support multi-selecting sub-issues to update them from the parent issue by selecting the checkbox beside each issue, or using X to select using your keyboard.
You can usually set the view to show or hide sub-issues in View Options. You can also use Filters to show only top-level (parent) issues, issues with sub-issues, or only sub-issues. If you use these filters frequently, consider creating a custom view.
When you view a sub-issue, we'll show a header at the top that lets you click to navigate to the parent issue or any of the other sub-issues.