Review collaboration identifies PR collaboration activities in your code review process. This report helps you improve your team’s processes and collaboration to get quality PRs merged quickly.
Use the metrics in Review collaboration for insight into how well a team is working together and where they may need help.
Team leads, managers, and scrum masters can:
- View team collaboration and responsiveness trends and use them during retrospectives.
- Reduce wait time for feedback to improve flow efficiency.
- See where the team may need help in collaboration and effectively merging well-reviewed PRs.
In this article
Review collaboration metrics
Review collaboration provides pull request data on team collaboration within the code review process. Use these metrics to see how well your team is collaborating on PRs.
The metrics in Review collaboration are split into Submitter and Reviewer metrics. Submitter metrics focus on the activities PR submitters take to drive a PR to merge. Reviewer metrics focus on the activities PR reviewers take to ensure quality PRs are ready to be merged.
Note: Review collaboration only considers merged PRs when calculating metrics. Trend percentages are calculated using linear regression. Trends only display when there are four or more complete Monday through Sunday weeks selected.
Use these metrics during a sprint to see if your team is improving their trends each sprint.
Learn more about pull request and collaboration metrics.
Collaboration map
Use the Collaboration map to tie together submitter and reviewer activity to show who is collaborating on PRs.
Note: PRs are included in the Reviewer column if they are merged in the selected date range and have a non-excluded comment. PRs are not included in the Reviewer column if the only reviewer action is an approval that isn’t a comment or the PR is excluded via regular expression. Approvals from vendors like BitBucket, GitLab, and Azure DevOps do not count as comments. Approvals from GitHub count as comments. To ensure PRs count as reviewed, consider adding a short comment to PRs when they are approved.
Hover over Submitter or Reviewer names to see who’s reviewing whose PRs and gauge how your team is collaborating. For example, you might expect your senior engineers to do a lot of reviewing for a lot of different users. You might see users working on specialized projects to review in small groups.
Use this report to gain insight into your team’s dynamic. For example, you might watch for people who consistently partner up and review each other's work without helping the rest of the team.
Use this data to open conversations and improve your team’s collaboration and knowledge sharing practices.
Review radar
The Review radar graph shows how code reviews are distributed throughout the team by identifying which users collaborate on PRs and how many PRs they review within the selected time period.
Use the x-axis to view how many different users’ PRs were reviewed by a user. Use the y-axis to view the total number of PRs the user reviewed.
Hover over a circle to view users and who they collaborated with.
The graph shows how many reviews and reviewees a user has. Users in the top right of Review radar are reviewing several PRs for multiple teammates.
Tip: Users in the top right corner of Review radar are often impactful knowledge-holders in your teams. Talk with them to find ways to help pass along this knowledge to other reviewers and reduce the review burden on your most impactful team members. Users in the top left corner of Review radar tend to review a lot of PRs, but only for select individuals. Discuss their workload and areas of review to see if there’s an opportunity to broaden their review base, or understand any blockers that may limit their review coverage.
The thickness of the line connecting two people is a visual indication of how many of their PRs they've reviewed. A thicker line indicates more reviewed PRs.
Solid circles represent users on a team. Hollow circles represent users not on the team. Use the search bar to find where a specific user is located on the radar.
Use insights from Review radar to find where you can increase knowledge shared and engagement in the review process.
For example, you may expect to see senior engineers reviewing more PRs and pairing with newer engineers, though it might vary depending on the context of the user and their projects. If these trends aren’t aligning with your expectations, start a conversation with your team focused on creating better collaboration practices.