gitlab-org--gitlab-foss/doc/user/analytics/code_review_analytics.md

1.5 KiB

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

Code review analytics (PREMIUM)

Moved to GitLab Premium in 13.9.

Use code review analytics to view review metrics per merge request and make improvements to your code review process:

  • A high number of comments or commits may indicate:
    • The code 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.
  • Fewer comments and approvers may indicate staffing requirements.

Code review analytics displays a table of open merge requests that have at least one non-author comment. The review time is measured from when the first non-author comment was submitted.

View code review analytics

Prerequisite:

  • You must have at least the Reporter role.

To view code review analytics:

  1. On the top bar, select Main menu > Projects and find your project.
  2. On the left sidebar, select Analytics > Code Review.
  3. Filter merge requests by milestone and label.