summaryrefslogtreecommitdiff
path: root/doc/user/analytics/code_review_analytics.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/user/analytics/code_review_analytics.md')
-rw-r--r--doc/user/analytics/code_review_analytics.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/user/analytics/code_review_analytics.md b/doc/user/analytics/code_review_analytics.md
index dc956765794..745774480b0 100644
--- a/doc/user/analytics/code_review_analytics.md
+++ b/doc/user/analytics/code_review_analytics.md
@@ -1,8 +1,8 @@
---
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.
stage: Manage
-group: Value Stream Management
-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/#designated-technical-writers
+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
---
@@ -16,7 +16,7 @@ enables you to:
1. Take action on individual merge requests.
1. Reduce overall cycle time.
-NOTE: **Note:**
+NOTE:
Initially, no data appears. Data is populated as users comment on open merge requests.
## Overview
@@ -37,7 +37,7 @@ The table is sorted by:
## Use cases
-This feature is designed for [development team leaders](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead)
+This feature is designed for [development team leaders](https://about.gitlab.com/handbook/marketing/strategic-marketing/roles-personas/#delaney-development-team-lead)
and others who want to understand broad code review dynamics, and identify patterns to explain them.
You can use Code Review Analytics to: