We’ve made a few important updates to improve groups—including more robust configurations, easier management, and clearer representation of memberships. There is no change to any of your metrics as a result of these changes.

—

New Membership History

Set a Join and/or Departure date on a group member to limit their data to a specific window of time. Members with a Departure date can be found under the Past tab under Members.

Use this feature to more accurately reflect teams where members are changing over time. You can also exclude data for managers that were previously ICs while retaining the data before they changed roles. To compare AI coding tools, use this feature to limit data for each developer in the group to after they started using the tool.

History of members joining or departing a group is automatically retained for teams synced from your Git provider (e.g. GitHub Teams). You will now see Join and Departure dates displayed for members of these synced groups. There is no change to your metrics as a result of this change, unless you choose to manually modify Join and Departure dates.

Faster, More Efficient Group Management

We’ve implemented a faster, more efficient user interface for adding members to groups. You can now add members to groups from the Git Users page.

You can add multiple membership records for a single user, spanning different periods of time. Use this feature to capture users that joined, left, and then rejoined a group. There is no change to bulk add or delete members from a group, aside from a small change to the terminology (“delete” vs. “remove”).

Clearer Representation of Group Membership

Group membership counts—as shown next to each group for context—have been updated to include Git users marked as excluded (e.g. managers) or bots. Previously, these users were not included in the count.

Contextual member counts are no longer displayed for groups in KPIs, Leading Indicators, and Comparisons to avoid confusion. Instead, a count of developers—anyone who created a pull request in the last 90 days—is now shown for metric drilldowns when it is relevant, such as for New Deliveries per Developer, Code Review Participation, and Open Pull Requests per Developer.

As a reminder, you can exclude pull requests created by a user (e.g. managers, product managers, designers, and other Git users outside of engineering). Reviews and approvals from these users will still count towards the progress of your pull requests to preserve accuracy (e.g. calculating Time to Review), but they will not factor into contributor-based metrics (e.g., Developer, Reviewer, and Contributor counts). You can also exclude all pull request activity for a specific user. Their reviews and other pull request activity are not factored into any metrics.

—

These changes aim to provide more accurate data and a more intuitive interface for managing group memberships. If you have questions, please reach out to us at support@software.com.