Nested Teams
Coordinate multiple development teams by grouping them together within a single parent team. Share team labels, cycles, issue workflows, and templates across multiple teams.
Overview
In complex organizations, nested teams allow organizing work in sensible units through a layer of nesting. Team-specific concepts like cycles, workflows and labels set in a parent team are inherited by its sub-teams to maintain alignment throughout these groups.
Create a sub-team
From an existing team, go Settings > Teams > General and select another existing team as its parent. Taking this action requires admin permissions.
Shared concepts
Workflow
Workflow settings are inherited from the parent team; all sub-teams will have the exact same list of issue statuses as their parent team.
Cycles
Cycles are parent-enforced; if a parent team has a cycles schedule defined, all sub-teams will inherit the same schedule. If the parent has no schedule then sub-teams may define their own schedule.
When merging a sub-team cycle schedule with a parent's, past cycles remain un-touched. The current and upcoming cycles of the sub-team update to the closest parent cycles.
Labels
Labels scoped to a parent team will also be available for use in their sub-teams. Sub-teams may create their own labels specific to their own context.