Add latest changes from gitlab-org/gitlab@master

8 files changed, 36 insertions, 26 deletions

diff --git a/doc/administration/dedicated/index.md b/doc/administration/dedicated/index.md
index db30684ab1c..0a5a3f702bf 100644
--- a/doc/administration/dedicated/index.md
+++ b/doc/administration/dedicated/index.md
@@ -59,7 +59,7 @@ If you want your GitLab data to be encrypted at rest, the KMS keys used must be
 
 If you use a key per service, all services must be encrypted at rest. Selective enablement of this feature is not supported.
 
-The keys provided have to reside in the same primary and secondary region specified during [onboarding](#onboarding).
+The keys provided have to reside in the same primary, secondary and backup region specified during [onboarding](#onboarding).
 
 For instructions on how to create and manage KMS keys, visit [Managing keys](https://docs.aws.amazon.com/kms/latest/developerguide/getting-started.html) in the AWS KMS documentation.
 
@@ -156,6 +156,8 @@ The last page asks you to confirm the KMS key policy. It should look similar to
 }
 ```
 
+Make sure the AWS KMS keys are replicated to your desired primary, secondary and backup region specified during [onboarding](#onboarding).
+
 ### Inbound Private Link
 
 [AWS Private Link](https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html) allows users and applications in your VPC on AWS to securely connect to the GitLab Dedicated endpoint without network traffic going over the public internet.
diff --git a/doc/integration/jira/connect-app.md b/doc/integration/jira/connect-app.md
index 0c218d17c33..0bed1f29c9f 100644
--- a/doc/integration/jira/connect-app.md
+++ b/doc/integration/jira/connect-app.md
@@ -16,7 +16,7 @@ You can use the GitLab for Jira Cloud app to link top-level groups or subgroups.
   - [Connect the GitLab for Jira Cloud app for self-managed instances](#connect-the-gitlab-for-jira-cloud-app-for-self-managed-instances) (GitLab 15.7 and later).
   - [Install the GitLab for Jira Cloud app manually](#install-the-gitlab-for-jira-cloud-app-manually).
 
-If you use Jira Data Center or Jira Server, use the [Jira DVCS connector](dvcs/index.md) instead.
+If you use Jira Data Center or Jira Server, use the [Jira DVCS connector](dvcs/index.md) developed and maintained by Atlassian.
 
 ## Install the GitLab for Jira Cloud app **(FREE SAAS)**
 
diff --git a/doc/integration/jira/development_panel.md b/doc/integration/jira/development_panel.md
index c444ffe8a3b..feee089da2e 100644
--- a/doc/integration/jira/development_panel.md
+++ b/doc/integration/jira/development_panel.md
@@ -9,8 +9,8 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 You can use the Jira development panel to view GitLab activity for a Jira issue directly in Jira.
 To set up the Jira development panel:
 
-- **For Jira Cloud**, use the [GitLab for Jira Cloud app](connect-app.md) developed by GitLab.
-- **For Jira Data Center or Jira Server**, use the [Jira DVCS connector](dvcs/index.md) developed by Atlassian.
+- **For Jira Cloud**, use the [GitLab for Jira Cloud app](connect-app.md) developed and maintained by GitLab.
+- **For Jira Data Center or Jira Server**, use the [Jira DVCS connector](dvcs/index.md) developed and maintained by Atlassian.
 
 <i class="fa fa-youtube-play youtube" aria-hidden="true"></i>
 For an overview, see [Jira development panel integration](https://www.youtube.com/watch?v=VjVTOmMl85M).
@@ -49,11 +49,16 @@ depends on where you mention the Jira issue ID in GitLab.
 
 | GitLab: where you mention the Jira issue ID    | Jira development panel: what information is displayed |
 |------------------------------------------------|-------------------------------------------------------|
-| Merge request title or description             | Link to the merge request<br>Link to the deployment<br>Link to the pipeline by title only and by description ([introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/390888) in GitLab 15.10)<br>Link to the branch ([introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/354373) in GitLab 15.11) |
+| Merge request title or description             | Link to the merge request<br>Link to the deployment<br>Link to the pipeline through merge request title<br>Link to the pipeline through merge request description <sup>1</sup><br>Link to the branch <sup>2</sup> |
 | Branch name                                    | Link to the branch<br>Link to the deployment                                    |
-| Commit message                                 | Link to the commit<br>Link to the deployment from up to 5,000 commits after the last successful deployment to the environment ([introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/300031) in GitLab 16.2 [with a flag](../../administration/feature_flags.md) named `jira_deployment_issue_keys`. Enabled by default) |
+| Commit message                                 | Link to the commit<br>Link to the deployment from up to 5,000 commits after the last successful deployment to the environment <sup>3</sup> <sup>4</sup> |
 | [Jira Smart Commit](#jira-smart-commits)       | Custom comment, logged time, or workflow transition   |
 
+1. [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/390888) in GitLab 15.10.
+1. [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/354373) in GitLab 15.11.
+1. [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/300031) in GitLab 16.2 [with a flag](../../administration/feature_flags.md) named `jira_deployment_issue_keys`. Enabled by default.
+1. [Generally available](https://gitlab.com/gitlab-org/gitlab/-/issues/415025) in GitLab 16.3. Feature flag `jira_deployment_issue_keys` removed.
+
 ## Jira Smart Commits
 
 Prerequisites:
diff --git a/doc/integration/jira/dvcs/index.md b/doc/integration/jira/dvcs/index.md
index 3ebbc9a921d..2f484662218 100644
--- a/doc/integration/jira/dvcs/index.md
+++ b/doc/integration/jira/dvcs/index.md
@@ -13,6 +13,8 @@ The Jira DVCS connector was also deprecated and removed for Jira 8.13 and earlie
 
 Use the Jira DVCS (distributed version control system) connector if you self-host
 your Jira instance with Jira Data Center or Jira Server and want to use the [Jira development panel](../development_panel.md).
+The Jira DVCS connector is developed and maintained by Atlassian. For more information, see the
+[Atlassian documentation](https://confluence.atlassian.com/adminjiraserver/integrating-with-development-tools-using-dvcs-1047552689.html).
 
 If you're on Jira Cloud, migrate to the GitLab for Jira Cloud app. For more information, see [Install the GitLab for Jira Cloud app](../connect-app.md#install-the-gitlab-for-jira-cloud-app).
 
diff --git a/doc/integration/jira/index.md b/doc/integration/jira/index.md
index dbda2e91dee..08942b61f87 100644
--- a/doc/integration/jira/index.md
+++ b/doc/integration/jira/index.md
@@ -28,8 +28,8 @@ You can use the [Jira issue integration](configure.md) developed by GitLab with
 You can use the [Jira development panel](development_panel.md) to [view GitLab activity for an issue](https://support.atlassian.com/jira-software-cloud/docs/view-development-information-for-an-issue/)
 including related branches, commits, and merge requests. To configure the Jira development panel:
 
-- **For Jira Cloud**, use the [GitLab for Jira Cloud app](connect-app.md) developed by GitLab.
-- **For Jira Data Center or Jira Server**, use the [Jira DVCS connector](dvcs/index.md) developed by Atlassian.
+- **For Jira Cloud**, use the [GitLab for Jira Cloud app](connect-app.md) developed and maintained by GitLab.
+- **For Jira Data Center or Jira Server**, use the [Jira DVCS connector](dvcs/index.md) developed and maintained by Atlassian.
 
 ## Jira integration capabilities
 
diff --git a/doc/subscriptions/customers_portal.md b/doc/subscriptions/customers_portal.md
index 25f36432f4b..96d28a2755d 100644
--- a/doc/subscriptions/customers_portal.md
+++ b/doc/subscriptions/customers_portal.md
@@ -25,12 +25,16 @@ To sign in to Customers Portal using your GitLab.com account:
 1. Navigate to [Customers Portal](https://customers.gitlab.com/customers/sign_in).
 1. Select **Continue with your GitLab.com account**.
 
-To sign in to Customers Portal using your email and password:
+To sign in to Customers Portal with your email and to receive a one-time sign-in link:
 
 1. Navigate to [Customers Portal](https://customers.gitlab.com/customers/sign_in).
-1. Select **Sign in with your email and password**.
-1. Provide the **Email** and **Password** for your Customers Portal account.
-1. Select **Sign in**.
+1. Select **Sign in with your email**.
+1. Provide the **Email** for your Customers Portal account. You will receive 
+   an email with a one-time, sign-in link for your Customers Portal account.
+1. In the email you received, select **Sign in**.
+
+NOTE:
+The one-time sign-in link expires in 24 hours and can only be used once.
 
 ## Change account owner information
 
@@ -47,7 +51,6 @@ To change account owner information, including name, billing address, and email
 If you want to transfer ownership of the Customers Portal account
 to another person, after you enter that person's personal details, you must also:
 
-- [Change the Customers Portal account password](#change-customers-portal-account-password).
 - [Change the linked GitLab.com account](#change-the-linked-account), if you have one linked.
 
 ## Change your company details
@@ -111,15 +114,6 @@ To change the GitLab.com account linked to your Customers Portal account:
 1. Under **Your GitLab.com account**, select **Change linked account**.
 1. Sign in to the [GitLab.com](https://gitlab.com/users/sign_in) account you want to link to the Customers Portal account.
 
-## Change Customers Portal account password
-
-To change the password for this customers portal account:
-
-1. Sign in to the [Customers Portal](https://customers.gitlab.com/customers/sign_in).
-1. Select the **My account** dropdown list and select **Account details**.
-1. Make the required changes to the **Your password** section.
-1. Select **Save changes**.
-
 ## Customers that purchased through a reseller
 
 If you purchased a subscription through an authorized reseller (including GCP and AWS marketplaces), you have access to the Customers Portal to:
diff --git a/doc/user/analytics/analytics_dashboards.md b/doc/user/analytics/analytics_dashboards.md
index 2f61f172b04..2bba2d6df17 100644
--- a/doc/user/analytics/analytics_dashboards.md
+++ b/doc/user/analytics/analytics_dashboards.md
@@ -24,17 +24,24 @@ filters and visualizations to query and retrieve results.
 The following data sources are configured for analytics dashboards:
 
 - [Product analytics](../product_analytics/index.md)
+- [Value Stream Management](../analytics/value_streams_dashboard.md)
 
 ## Built-in dashboards
 
-To help you get started with analytics, GitLab provides two built-in dashboards with predefined visualizations:
+To help you get started with analytics, GitLab provides built-in dashboards with predefined visualizations.
 
-- **Audience**, which displays metrics related to traffic, such as number of users and sessions.
-- **Behavior**, which displays metrics related to user activity, such as number of page views and events.
+### Product analytics
+
+- **Audience** displays metrics related to traffic, such as the number of users and sessions.
+- **Behavior** displays metrics related to user activity, such as the number of page views and events.
 
 These dashboards are labeled **By GitLab**, and you cannot edit them.
 Instead, you can create a custom dashboard with a similar style.
 
+### Value Stream Management
+
+- **Value Streams Dashboard** displays metrics related to [DevOps performance, security exposure, and workstream optimization](../analytics/value_streams_dashboard.md#devops-metrics-comparison-panel).
+
 ## Custom dashboards
 
 With custom dashboards, you can design and create visualizations for the metrics that are most relevant to your use case.
diff --git a/doc/user/analytics/index.md b/doc/user/analytics/index.md
index c057a8b193d..50ba7ffc0e4 100644
--- a/doc/user/analytics/index.md
+++ b/doc/user/analytics/index.md
@@ -39,7 +39,7 @@ You can use GitLab to review analytics at the project level. Some of these featu
 - [CI/CD & DORA](ci_cd_analytics.md)
 - [Code Review](code_review_analytics.md)
 - [Insights](../project/insights/index.md)
-- [Issue](../group/issues_analytics/index.md)
+- [Issue](../../user/analytics/issue_analytics.md)
 - [Merge Request](merge_request_analytics.md), enabled with the `project_merge_request_analytics`
   [feature flag](../../development/feature_flags/index.md#enabling-a-feature-flag-locally-in-development)
 - [Repository](repository_analytics.md)