We’ve added support for nesting groups within groups, allowing you to more easily visualize data according to your organization's structure. Changes to child groups will be reflected in parent groups, reducing the time required to manage and update groups.

Here’s a quick overview of the improvements you’ll see across the platform:

Nested Group Filter

The group filter is now organized by group hierarchy, allowing you to navigate through groups according to your organization’s structure.

Drilldowns

Filtering to a parent group also displays child groups within the group breakdown table, allowing you to more easily compare metrics across groups.

Group Settings

You can now assign child groups to a parent group. Parent groups will automatically inherit the members and repositories assigned to child groups.

Here’s an example of how it all works:

• You create a group called Product Engineering.
• You add three child groups to Product Engineering: Mobile App, Web App, and APIs.
• Product Engineering inherits the members and repositories assigned to each of the three child groups. That means removing a member or repository from a child group will also remove them from the parent group.
• You can assign additional members directly to Product Engineering (e.g., Managers or Staff Engineers that might oversee all three teams) without affecting child member inheritance.
• If you choose to assign repositories to Product Engineering, repositories will not be inherited from child groups. This allows you to ignore contributions to certain child group repositories that may not be representative of the parent group’s work.
• Members can have multiple membership records. For example, if someone leaves and then rejoins a team, you can set join and departure dates to accurately capture that member’s tenure and contributions on each team.

Child Membership Updates for Imported Groups (GitHub Teams and GitLab Groups)

• Previously, members of a child group were automatically added as direct members to the parent group.
• With this update, child group members are now shown as inherited members of the parent group instead of being added directly.
• To support this change, their former direct memberships were marked as “removed,” which is why they now appear in the Past members list.
• This change will have no effect on your data.

These updates give you more control and visibility into group structures and history—especially useful for large or dynamic teams.

If you have questions, please reach out to us at support@software.com.