2020-01-17 19:09:18 -05:00
---
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-05 17:09:42 -04:00
stage: Manage
2020-11-19 13:09:13 -05:00
group: Optimize
2020-11-26 01:09:20 -05:00
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-01-17 19:09:18 -05:00
---
2020-05-05 17:09:42 -04:00
2020-01-17 19:09:18 -05:00
# Code Review Analytics **(STARTER)**
2020-05-21 23:08:28 -04:00
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/38062) in [GitLab Starter](https://about.gitlab.com/pricing/) 12.7.
2020-01-17 19:09:18 -05:00
2020-09-15 14:09:43 -04:00
Code Review Analytics makes it easy to view the longest-running reviews among open merge requests and
enables you to:
1. Take action on individual merge requests.
1. Reduce overall cycle time.
2020-01-17 19:09:18 -05:00
2020-12-04 16:09:29 -05:00
NOTE:
2020-09-15 14:09:43 -04:00
Initially, no data appears. Data is populated as users comment on open merge requests.
2020-01-17 19:09:18 -05:00
## Overview
2020-01-28 01:09:01 -05:00
Code Review Analytics 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-01-21 19:08:47 -05:00
2020-09-15 14:09:43 -04:00
To access Code Review Analytics, from your project's menu, go to **Project Analytics > Code Review** .
You can filter the list of merge requests by milestone and label.
2020-01-28 01:09:01 -05:00
2020-01-20 19:08:46 -05:00
2020-09-15 14:09:43 -04:00
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-01-20 19:08:46 -05:00
2020-01-21 19:08:47 -05:00
## Use cases
2020-01-20 19:08:46 -05:00
2020-12-03 19:09:55 -05:00
This feature is designed for [development team leaders ](https://about.gitlab.com/handbook/marketing/strategic-marketing/roles-personas/#delaney-development-team-lead )
2020-09-15 14:09:43 -04:00
and others who want to understand broad code review dynamics, and identify patterns to explain them.
2020-01-17 19:09:18 -05:00
2020-09-15 14:09:43 -04:00
You can use Code Review Analytics to:
2020-01-20 19:08:46 -05:00
2020-09-15 14:09:43 -04:00
- Expose your team's unique challenges with code review.
- Identify improvements that might substantially accelerate your development cycle.
2020-01-20 19:08:46 -05:00
- Your team agrees that code review is moving too slow.
2020-02-07 16:08:39 -05:00
- The [Value Stream Analytics feature ](value_stream_analytics.md ) shows that reviews are your team's most time-consuming step.
2020-09-15 14:09:43 -04:00
- Analyze the patterns and trends of different types of work that are moving slow.
2020-01-20 19:08:46 -05:00
2020-09-15 14:09:43 -04:00
For example:
2020-01-20 19:08:46 -05:00
- 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.
2020-01-17 19:09:18 -05:00
## Permissions
- On [Starter or Bronze tier ](https://about.gitlab.com/pricing/ ) and above.
2020-01-20 19:08:46 -05:00
- By users with Reporter access and above.
