Review collaboration

Tags: Flow

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 time to merge PRs.


In this article



How do I view 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.

back to top


How do I view who is reviewing submitted code?

Review collaboration maps submitter and reviewer activity to show who is collaborating on PRs.

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.

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.

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. 

Submitter and reviewer activity in the Review collaboration report

back to top


How do I view an individual’s collaboration data?

Click a user’s name to view their individual collaboration data. See who is working well together and who might need a nudge to review someone’s code.

Viewing a submitter's metrics

Click a submitter's name to view their submitted PRs over the selected time period.

Detailed view of a submitter's metrics in the Review collaboration report

Hover over a PR to see more info. Click a PR, then click View PR in the resulting dropdown menu to open the PR in a new window.

Click the X in the top right corner to return to the Review collaboration overview.

Viewing a reviewer's metrics

Click a reviewer’s name to see their reviewed PRs over the selected period.

Detailed view of s reviewer's metrics in the Review collaboration report

Hover over a PR to see more info. Click a PR, then click View PR in the resulting dropdown menu to open the PR in a new window.

Click the X in the top right corner to return to the Review collaboration overview.

back to top


If you need help, please contact Pluralsight Support.