Review Collaboration

Understand how your engineering teams work collaboratively. Effectively communicate the healthy tension between speed and thoroughness in code review.

The Review Collaboration provides code collaboration stats between submitters and reviewers. Users can select the team’s review collaboration stats to view, repositories to analyze, and a timeframe for analysis.

3026

Submitter and Reviewer Metrics

This feature offers several metrics to help users measure the effectiveness of the code review process. These metrics include:

  • Responsiveness and Reaction Time: This metric measures how quickly team members respond to and communicate with each other during reviews. A healthy code review workflow should aim to improve the velocity of code review communication.

  • Involvement: This metric represents the percentage of Pull Requests (PRs) a reviewer participated in. It provides a measure of engineering engagement in the code review process.

  • Comments Addressed: This metric measures the percentage of reviewer comments that were responded to with a comment or a code revision.

  • Receptiveness: This metric is the ratio of follow-on commits to comments, indicating openness to constructive feedback.

  • Influence: This metric measures the ratio of follow-on commits made after the reviewer commented, providing insight into the likelihood that reviewers’ comments will lead to a follow-on commit.

  • Unreviewed PRs: This metric measures the number of Pull Requests that are open and merged without ever getting a comment, which should be as close to zero as possible to ensure thoroughness of feedback.

  • Review Coverage: This metric indicates the number of pull requests that have been merged after review and should be as close to 100% as possible.

Sharing Index

The Sharing Index report is a visualization of the evolution of knowledge sharing throughout the organization. It is the ratio of active reviewers to submitters.
Active reviewers are users who actually reviewed a PR in the selected time period, while submitters represent the total number of users who submitted a PR in the selected time period.

Collaboration Map

The Collaboration Map shows a map of code collaboration, indicating which engineers reviewed whose pull requests.
If you hover over an engineer's name in the left column, you will see who reviewed their PRs.
If you hover over an engineer’s name in the right column, you will see whose pull requests he/ she reviewed.

2996