Sub-teams
Nest a team under a parent. A child with no cycle policy of its own follows the parent cadence.
Group sub-teams underneath a parent team. Estimates, labels, and membership stay on the child. Cycle cadence follows the parent until you Set own cadence.
Overview
Sub-teams let you reflect how groups sit under a larger unit without hiding the child's work. Create a child to split specialized work while the parent stays the umbrella in Your teams.
A nested team with no cycle policy of its own follows the nearest ancestor that has one. Settings then show Inherited from that parent. Parent changes apply to future cycles; completed history stays as it was. Estimates stay on that team. Issue statuses are workspace-wide.
Basics
Update an existing team to a sub-team
Go to Settings → Your teams → <team> and set Parent team under Team hierarchy. Confirm Change parent team? if Pulse previews capability changes. Workspace managers and team managers who can update the team can reparent it. Workspace plans can cap how deep the tree may go.
Create a new sub-team
When creating a team, optionally choose Set parent team.
Configure a sub-team
After you nest a team, open its settings and confirm what should stay independent: estimates, labels, templates, and Source control workflow.
If Cycles settings show Inherited from the parent, the child is following that cadence. Use Set own cadence to copy the values and stop following. See Cycles.
Un-nesting a sub-team
In the child's settings, set Parent team to No parent team. The team becomes a root in Your teams. Cycle inherit stops because there is no parent to follow. Labels, statuses, and members are not stripped.
Multi level sub-teams
You can nest more than one level. Depth is limited by the workspace plan. Reparenting a branch moves its descendants with it.
Parent and sub-team settings
Parent team feature settings inherited by sub-teams
Membership is not forced up the tree: someone can belong to a child without belonging to the parent. In Your teams, child teams you can reach still nest under the nearest ancestor you can see.
| Feature | Inheritance |
|---|---|
| Membership | Independent. Parent membership is not required for a sub-team seat |
| Status | Workspace-wide. Children do not inherit a separate workflow |
| Cycles | Follows the parent when the child has no cycle policy of its own. Use Set own cadence to diverge |
| Estimates | Independent. Configure each team under General |
Parent team feature settings accessible to sub-teams
Sub-teams can use their own labels, templates, and views. Parent-team views can include issues from child teams you can access.
Independent feature settings in sub-teams
Customize these on the child:
- Team timezone (on cycle policy)
- GitHub/GitLab automations (Source control workflow)
- Triage Intelligence and request SLAs
Last updated on