Coordinate multiple development teams by grouping them together within a single parent team. Share labels, cycles and issue statuses across nested teams.

Overview⁠

In complex organizations, nesting teams allows organizing work in sensible units. Team-specific concepts like cycles, workflows and labels set in a parent team are directly inherited by its sub-teams to maintain alignment throughout these groups.

Basics⁠

Create a sub-team⁠

When creating a new team, designate it as nested under another existing team. If you have an existing team you wish to turn into a sub-team, go Settings > Teams > General and select another existing team as its parent. This action requires admin permissions.

To protect the privacy of private teams, a private parent team may have only private sub-teams.

Configure a sub-team⁠

Once you've designated one team as nested under another, a wizard will take you through any conflicts that need to be resolved to finalize nesting the teams, like normalizing statuses between parent and sub-team or resolving duplicate label conflicts.

Check nested and parent team settings⁠

Once you nest teams, verify that the settings of your nested and parent teams fit your expectations. Settings like your GitHub PR automations should be verified to ensure they meet your expectations after nesting.

Shared concepts⁠

Status⁠

Issue status settings are inherited from the parent team; all sub-teams will have the exact same list of issue statuses as their parent team.

Cycles⁠

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⁠

In the same way that an issue in a team can take a workspace or team label, sub-teams add another layer. An issue in a sub-team can take labels scoped to that sub-team, its parent team, or the workspace.

Membership⁠

If you are a member of a sub-team, it's required to be a member of the parent team as well.

Views⁠

Sub-teams can have dedicated views. Issues in sub-teams are accessible in the views stored in their parent teams.