gitlabhq/doc/user/analytics/code_review_analytics.md

stage, group, info, description, title

stage	group	info	description	title
Plan	Optimize	To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments	Learn how long your open merge requests have spent in code review, and what distinguishes the longest-running.	Code review analytics

{{< details >}}

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated

{{< /details >}}

{{< history >}}

• Moved to GitLab Premium in 13.9.

{{< /history >}}

Code review analytics displays a table of open merge requests that have at least one non-author comment. The review time is the amount of time since the first comment by a non-author in a merge request.

You can use code review analytics to view review metrics per merge request and improve your code review process.

• A high number of comments or commits may indicate:
  • Code that is too complex.
  • Authors who require more training.
• A long review time may indicate:
  • Types of work that move slower than other types.
  • Opportunities to accelerate your development cycle.
• Few comments and approvers may indicate a lack of available team members.

For a video explanation, see Code review analytics: Faster code review.

View code review analytics

Prerequisites:

• You must have at least the Reporter role.

To view code review analytics:

1. On the left sidebar, select Search or go to and find your project.
2. Select Analyze > Code review analytics.
3. Optional. Filter results:
   1. Select the filter bar.
   2. Select a parameter. You can filter merge requests by milestone and label.
   3. Select a value for the selected parameter.

The table shows up to 20 merge requests in review per page, and includes the following information about each merge request:

• Merge request title
• Review time
• Author
• Approvers
• Comments
• Commits
• Line changes