Use Team health insights to gain an understanding of your teams’ health. View information related to your teams’ coding processes and code collaboration. This information helps you investigate and diagnose potential issues as well as see where your team is succeeding.
Who can use this?
Team health insights metrics
Team health insights shows your teams’ work across a collection of ten coding and collaboration metrics. These metrics give you visibility into your teams’ activity in commits and PRs across three categories: culture, activity, and efficiency.
Team health insights shows two years of data. Data older than two years does not factor into the metrics.
Note: PR data from ADO Services and ADO Server is only available starting from six months before the integration is first processed, at the earliest.
Use the Edit metrics dropdown menu in the top right corner to select which metrics you want to view.
Note: Users on a Core plan only have access to select Team health insights metric.
There are a few ways to approach the decision of which metrics to view, depending on your goals for the report:
- Decide which metrics you want to use to drive change on your team, then deselect all other metrics to make your most important metrics visible.
- Select one metric from each of the categories to get a more holistic view of metrics across your team.
- Select only commit metrics to dive deeper into your teams’ coding practices.
- Select only PR collaboration metrics to see how your team is working together to release code.
Whatever way you decide to choose metrics, make sure you customize the report to help you achieve your goals. Selecting only the metrics most important to you gives you the information you need to focus on team goals without extra noise. Change the metrics you’ve selected at any time to get a different view of your teams’ health.
Learn more about Team health insights metrics.
How do I use Team health insights?
Engineering leaders can use Team health insights to view commit and PR collaboration activity trends over time. Use this information to gauge your teams’ health.
Use the filter at the top of the report to select the teams, repos, and date ranges you want to view metrics for.
The Team filter shows metrics for the selected team, including for:
- Commits authored by a member of the team
- Pull requests authored by a member of the team
- Pull requests commented on by a member of the team
The Date range filter shows metrics for the selected date range, including:
- Commits created during the date range
- Pull requests created during the date range
Note: Team health insights looks at the author date for commits, not the date the commit was pushed.
- The tiles at the top of the report show the averages for the metrics you select in the Edit metrics dropdown menu. A trend percentage displays if there are more than four complete Monday to Sunday weeks selected. The trend percentage is calculated using linear regression.
- The bar graph below the tiles shows the average for each metric over the selected period. A trend only displays if there are more than four complete Monday to Sunday weeks selected. The trend line is calculated using linear regression.
Important: The Team health insights report shows commits based on the local time zone of the commit author, not the time zone of the person viewing the report. If you want to see commits shown based on your time zone, use Work log. Because of this difference, the total number of coding days for a user may appear different between Team health insights and Work log.
How do I view a team's insights?
Below the Team health insights graph is a team-by-team view showing the average of a metric for each team. Click into a team to view the report filtered by that team.
Sort the teams alphabetically or reverse alphabetically, or by filtering metrics from high to low or low to high.
If you don't immediately see a team you're looking for, use the Search filter.
If you need help, please contact Pluralsight Support.