Commit 1bba0824 authored by Evan Read's avatar Evan Read

Merge branch 'code-review-analytics-screenshot' into 'master'

Add screenshot to code review analytics page, small text changes

Closes #198271

See merge request gitlab-org/gitlab!23644
parents 1897f18f 8b4d1166
......@@ -7,17 +7,19 @@ description: "Learn how long your open merge requests have spent in code review,
> [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/38062) in [GitLab Starter](https://about.gitlab.com/pricing/) 12.7.
Code Review Analytics makes it easy to view the longest-running reviews among open merge requests,
enabling you to take action on individual MRs and reduce overall cycle time.
enabling you to take action on individual merge requests and reduce overall cycle time.
NOTE: **Note:**
Initially, no data will appear. Data is populated as users comment on open merge requests.
## Overview
Code Review Analytics displays a table of open merge requests which are currently considered to be in code review.
The code review period for an MR is automatically identified as the time since the first non-author comment.
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.
The code review period for a merge request is automatically identified as the time since the first non-author comment.
To access Code Review Analytics, from your project's menu, go to **Project Analytics > Code Review**.
To access Code Review Analytics, from your project's menu, go to **{chart}** **Project Analytics > Code Review**.
![Code Review Analytics](img/code_review_analytics_v12_8.png "List of code reviews; oldest review first.")
- The table is sorted by review duration, helping you quickly find the longest-running reviews which may need intervention or to be broken down into smaller parts.
- You can filter the list of MRs by milestone and label.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment