Add latest changes from gitlab-org/gitlab@14-6-stable-eev14.6.0-rc42

7 files changed, 36 insertions, 22 deletions

diff --git a/doc/user/analytics/ci_cd_analytics.md b/doc/user/analytics/ci_cd_analytics.md
index e949f968c2b..f083f886924 100644
--- a/doc/user/analytics/ci_cd_analytics.md
+++ b/doc/user/analytics/ci_cd_analytics.md
@@ -11,7 +11,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 > [Renamed](https://gitlab.com/gitlab-org/gitlab/-/issues/38318) to CI/CD Analytics in GitLab 12.8.
 
 GitLab tracks the history of your pipeline successes and failures, as well as how long each pipeline
-ran. To view this information, go to **Analytics > CI/CD Analytics**.
+ran. To view this information for a project, go to **Analytics > CI/CD Analytics**.
 
 View successful pipelines:
 
diff --git a/doc/user/analytics/img/product_analytics_commits_per_mr_v14_4.png b/doc/user/analytics/img/product_analytics_commits_per_mr_v14_4.png
index 649416c02c0..2bfde7beead 100644
--- a/doc/user/analytics/img/product_analytics_commits_per_mr_v14_4.png
+++ b/doc/user/analytics/img/product_analytics_commits_per_mr_v14_4.png
diff --git a/doc/user/analytics/img/productivity_analytics_time_to_merge_v14_4.png b/doc/user/analytics/img/productivity_analytics_time_to_merge_v14_4.png
index b5d0dd4d2ea..0b30aff2c7a 100644
--- a/doc/user/analytics/img/productivity_analytics_time_to_merge_v14_4.png
+++ b/doc/user/analytics/img/productivity_analytics_time_to_merge_v14_4.png
diff --git a/doc/user/analytics/img/productivity_analytics_trendline_v14_4.png b/doc/user/analytics/img/productivity_analytics_trendline_v14_4.png
index da5d3aec957..e0b3c54dee2 100644
--- a/doc/user/analytics/img/productivity_analytics_trendline_v14_4.png
+++ b/doc/user/analytics/img/productivity_analytics_trendline_v14_4.png
diff --git a/doc/user/analytics/index.md b/doc/user/analytics/index.md
index 0cc21e3f390..6a157dbb5ae 100644
--- a/doc/user/analytics/index.md
+++ b/doc/user/analytics/index.md
@@ -100,29 +100,29 @@ We use the following terms to describe GitLab analytics:
       - All incidents are related to a [production environment](../../ci/environments/index.md#deployment-tier-of-environments).
       - Incidents and deployments have a strictly one-to-one relationship (meaning any incident is related to only one production deployment, and any production deployment is related to no more than one incident).
 
-- **Lead time:** The duration of your value stream, from start to finish. Different to 
-[Lead time for changes](#lead-time-for-changes). Often displayed in combination with "cycle time," 
-which is shorter. GitLab measures lead time from issue creation to issue close. GitLab displays lead 
+- **Lead time:** The duration of your value stream, from start to finish. Different to
+[Lead time for changes](#lead-time-for-changes). Often displayed in combination with "cycle time,"
+which is shorter. GitLab measures lead time from issue creation to issue close. GitLab displays lead
 time in [group-level Value Stream Analytics](../group/value_stream_analytics/index.md).
-- **Mean Time to Change (MTTC):** The average duration between idea and delivery. GitLab measures 
+- **Mean Time to Change (MTTC):** The average duration between idea and delivery. GitLab measures
 MTTC from issue creation to the issue's latest related merge request's deployment to production.
-- **Mean Time to Detect (MTTD):** The average duration that a bug goes undetected in production. 
+- **Mean Time to Detect (MTTD):** The average duration that a bug goes undetected in production.
 GitLab measures MTTD from deployment of bug to issue creation.
-- **Mean Time To Merge (MTTM):** The average lifespan of a merge request. GitLab measures MTTM from 
-merge request creation to merge request merge (and closed/un-merged merge requests are excluded). 
+- **Mean Time To Merge (MTTM):** The average lifespan of a merge request. GitLab measures MTTM from
+merge request creation to merge request merge (and closed/un-merged merge requests are excluded).
 For more information, see [Merge Request Analytics](merge_request_analytics.md).
-- **Mean Time to Recover/Repair/Resolution/Resolve/Restore (MTTR):** The average duration that a bug 
+- **Mean Time to Recover/Repair/Resolution/Resolve/Restore (MTTR):** The average duration that a bug
 is not fixed in production. GitLab measures MTTR from deployment of bug to deployment of fix.
-- **Throughput:** The number of issues closed or merge requests merged (not closed) in a period of 
+- **Throughput:** The number of issues closed or merge requests merged (not closed) in a period of
 time. Often measured per sprint. GitLab displays merge request throughput in [Merge Request Analytics](merge_request_analytics.md).
-- **Value Stream:** The entire work process that is followed to deliver value to customers. For example, 
-the [DevOps lifecycle](https://about.gitlab.com/stages-devops-lifecycle/) is a value stream that starts 
+- **Value Stream:** The entire work process that is followed to deliver value to customers. For example,
+the [DevOps lifecycle](https://about.gitlab.com/stages-devops-lifecycle/) is a value stream that starts
 with "plan" and ends with "monitor". GitLab helps you track your value stream using [Value Stream Analytics](value_stream_analytics.md).
-- **Velocity:** The total issue burden completed in some period of time. The burden is usually measured 
-in points or weight, often per sprint. For example, your velocity may be "30 points per sprint". GitLab 
+- **Velocity:** The total issue burden completed in some period of time. The burden is usually measured
+in points or weight, often per sprint. For example, your velocity may be "30 points per sprint". GitLab
 measures velocity as the total points or weight of issues closed in a given period of time.
 
 ## Lead time for changes
 
-"Lead Time for Changes" differs from "Lead Time" because it "focuses on measuring only the time to 
+"Lead Time for Changes" differs from "Lead Time" because it "focuses on measuring only the time to
 deliver a feature once it has been developed", as described in ([Measuring DevOps Performance](https://devops.com/measuring-devops-performance/)).
diff --git a/doc/user/analytics/productivity_analytics.md b/doc/user/analytics/productivity_analytics.md
index da55a0f093c..e1ba2f5565e 100644
--- a/doc/user/analytics/productivity_analytics.md
+++ b/doc/user/analytics/productivity_analytics.md
@@ -34,14 +34,14 @@ Metrics and visualizations of **merged** merge requests are available on a proje
 
 ### Time to merge
 
-The **Time to merge** histogram shows the number of merge requests and the number 
+The **Time to merge** histogram shows the number of merge requests and the number
 of days it took to merge after creation. Select a column to filter subsequent charts.
 
 ![Metrics for number of days merge requests per number of days](img/productivity_analytics_time_to_merge_v14_4.png)
 
 ### Trendline
 
-The **Trendline** scatterplot shows all merge requests on a certain date, 
+The **Trendline** scatterplot shows all merge requests on a certain date,
 and the days it took to complete the action and a 30 day rolling median. Select the dropdown to view:
 
 - Time from first commit to first comment.
@@ -55,15 +55,15 @@ and the days it took to complete the action and a 30 day rolling median. Select
 
 ### Commits and merge request size
 
-Under the **Trendline** scatterplot, the left-side histogram shows 
-the time taken (in hours) between commits and comments until the merge 
+Under the **Trendline** scatterplot, the left-side histogram shows
+the time taken (in hours) between commits and comments until the merge
 request is merged. Select the dropdown to view:
 
 - Time from first commit to first comment.
 - Time from first comment until last commit.
 - Time from last commit to merge.
 
-The right-side histogram shows the size or complexity of a merge request. 
+The right-side histogram shows the size or complexity of a merge request.
 Select the dropdown to view:
   
 - Number of commits per merge request.
@@ -74,7 +74,7 @@ Select the dropdown to view:
 
 ### Merge request list
 
-The **List** table shows a list of merge requests with their respective time duration metrics. 
+The **List** table shows a list of merge requests with their respective time duration metrics.
 
 Sort metrics by:
 
@@ -83,7 +83,7 @@ Sort metrics by:
 - Time from last commit to merge.
 
 Filter metrics by:
- 
+
 - Number of commits per merge request.
 - Number of lines of code per commit.
 - Number of files touched.
diff --git a/doc/user/analytics/value_stream_analytics.md b/doc/user/analytics/value_stream_analytics.md
index 9c1a8893f95..cb6b2e49f60 100644
--- a/doc/user/analytics/value_stream_analytics.md
+++ b/doc/user/analytics/value_stream_analytics.md
@@ -102,6 +102,20 @@ The **Time** metrics near the top of the page are measured as follows:
 
 - **Lead time**: Median time from issue created to issue closed.
 - **Cycle time**: Median time from first commit to issue closed. (You can associate a commit with an issue by [crosslinking in the commit message](../project/issues/crosslinking_issues.md#from-commit-messages).)
+- **Lead Time for Changes**: median duration between merge request merge and deployment to a production environment for all MRs deployed in the given time period. [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/340150) in GitLab 14.5 (Ultimate only).
+
+## Deployment metrics (**PREMIUM**)
+
+> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/337256) in GitLab 11.3.
+
+Value Stream Analytics exposes two deployment related metrics near the top of the page:
+
+- **Deploys:** The number of successful deployments in the date range.
+- **Deployment Frequency:** The average number of successful deployments.
+
+The deployment metrics calculation uses the same method as the
+[group-level Value Stream Analytics](../group/value_stream_analytics/index.md#how-metrics-are-measured).
+Both of them are based on the [DORA API](../../api/dora/metrics.md#devops-research-and-assessment-dora-key-metrics-api).
 
 ## How the stages are measured