2020-03-13 15:44:24 +05:30
---
description: "Learn how long your open merge requests have spent in code review, and what distinguishes the longest-running." # Up to ~200 chars long. They will be displayed in Google Search snippets. It may help to write the page intro first, and then reuse it here.
2020-05-24 23:13:21 +05:30
stage: Manage
2021-02-22 17:27:13 +05:30
group: Optimize
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
2020-03-13 15:44:24 +05:30
---
2020-05-24 23:13:21 +05:30
2021-03-11 19:13:27 +05:30
# Code Review Analytics **(PREMIUM)**
2020-03-13 15:44:24 +05:30
2021-03-11 19:13:27 +05:30
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/38062) in GitLab 12.7.
> - Moved to GitLab Premium in 13.9.
2020-03-13 15:44:24 +05:30
2021-03-11 19:13:27 +05:30
Use Code Review Analytics to view the longest-running reviews among open merge
requests, and:
2020-11-24 15:15:51 +05:30
2021-03-11 19:13:27 +05:30
- Take action on individual merge requests.
- Reduce overall cycle time.
2020-03-13 15:44:24 +05:30
2022-04-04 11:22:00 +05:30
Code Review Analytics is available to users with at least the Reporter role, and displays a table of open merge requests that have at least one non-author comment. The review time is measured from the time the first non-author comment was submitted.
2020-03-13 15:44:24 +05:30
2022-03-02 08:16:31 +05:30
NOTE:
Initially, no data appears. Data is populated as users comment on open merge requests.
2020-03-13 15:44:24 +05:30
2021-04-29 21:17:54 +05:30
2020-03-13 15:44:24 +05:30
2020-11-24 15:15:51 +05:30
The table is sorted by:
- **Review time**: Helping you to quickly find the longest-running reviews which may need intervention
or to be broken down into smaller parts.
- Other columns: Display the author, approvers, comment count, and line change (-/+) counts.
2020-03-13 15:44:24 +05:30
2022-03-02 08:16:31 +05:30
## View Code Review Analytics
To view Code Review Analytics:
1. On the top bar, select **Menu > Projects** and find your project.
1. On the left sidebar, select **Analytics > Code Review** .
1. Filter merge requests by milestone and label.
2020-03-13 15:44:24 +05:30
## Use cases
2022-05-07 20:08:51 +05:30
This feature is designed for [development team leaders ](https://about.gitlab.com/handbook/product/personas/#delaney-development-team-lead )
2020-11-24 15:15:51 +05:30
and others who want to understand broad code review dynamics, and identify patterns to explain them.
2020-03-13 15:44:24 +05:30
2020-11-24 15:15:51 +05:30
You can use Code Review Analytics to:
2020-03-13 15:44:24 +05:30
2020-11-24 15:15:51 +05:30
- Expose your team's unique challenges with code review.
- Identify improvements that might substantially accelerate your development cycle.
2020-03-13 15:44:24 +05:30
- Your team agrees that code review is moving too slow.
- The [Value Stream Analytics feature ](value_stream_analytics.md ) shows that reviews are your team's most time-consuming step.
2020-11-24 15:15:51 +05:30
- Analyze the patterns and trends of different types of work that are moving slow.
2020-03-13 15:44:24 +05:30
2020-11-24 15:15:51 +05:30
For example:
2020-03-13 15:44:24 +05:30
- Lots of comments or commits? Maybe the code is too complex.
- A particular author is involved? Maybe more training is required.
- Few comments and approvers? Maybe your team is understaffed.
