diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-05-22 18:10:05 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-05-22 18:10:05 +0300 |
commit | 4ec96676406da695de083b4f394290902da2a964 (patch) | |
tree | 55dddec9b7e2498f800b1851f0778e25997868cd /doc/user | |
parent | f2d662be68fb15a2b38abaff576693f2b8f2c2f3 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user')
-rw-r--r-- | doc/user/analytics/value_streams_dashboard.md | 7 | ||||
-rw-r--r-- | doc/user/group/index.md | 6 | ||||
-rw-r--r-- | doc/user/group/manage.md | 6 |
3 files changed, 10 insertions, 9 deletions
diff --git a/doc/user/analytics/value_streams_dashboard.md b/doc/user/analytics/value_streams_dashboard.md index 528783f45f9..b207dff1f11 100644 --- a/doc/user/analytics/value_streams_dashboard.md +++ b/doc/user/analytics/value_streams_dashboard.md @@ -4,7 +4,7 @@ group: Optimize info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Value Streams Dashboard (Beta) **(ULTIMATE)** +# Value Streams Dashboard **(ULTIMATE)** > - Introduced in GitLab 15.8 as a Closed [Beta](../../policy/alpha-beta-support.md#beta) feature [with a flag](../../administration/feature_flags.md) named `group_analytics_dashboards_page`. Disabled by default. > - Released in GitLab 15.11 as an Open [Beta](../../policy/alpha-beta-support.md#beta) feature [with a flag](../../administration/feature_flags.md) named `group_analytics_dashboards_page`. Enabled by default. @@ -21,17 +21,18 @@ For more information, see the [Value Stream Management category direction page]( Our initial use case is focused on providing the ability to compare software delivery metrics. This comparison can help decision-makers understand whether projects and groups are improving. -The beta version of the Value Streams Dashboard includes the following metrics: +The Value Streams Dashboard includes the following metrics: - [DORA metrics](dora_metrics.md) - [Value Stream Analytics (VSA) - flow metrics](../group/value_stream_analytics/index.md) +- [Vulnerabilities](https://gitlab.com/gitlab-org/gitlab/-/security/vulnerability_report) metrics. The Value Streams Dashboard allows you to: - Aggregate data records from different APIs. - Track software performance (DORA) and flow of value (VSA) across the organization. -## DevOps metrics comparison +## DevOps metrics comparison panel The DevOps metrics comparison displays DORA4 and flow metrics for a group or project in the month-to-date, last month, the month before, and the past 180 days. diff --git a/doc/user/group/index.md b/doc/user/group/index.md index 7e093ccb01b..9ebf3be3000 100644 --- a/doc/user/group/index.md +++ b/doc/user/group/index.md @@ -21,10 +21,10 @@ For larger organizations, you can also create [subgroups](subgroups/index.md). For more information about creating and managing your groups, see [Manage groups](manage.md). NOTE: -Self-managed customers should create a top-level group so you can see an overview of -your organization. For more information about efforts to create an +For self-managed customers it could be beneficial to create one single top-level group, so you can see an overview of +your entire organization. For more information about efforts to create an organization view of all groups, [see epic 9266](https://gitlab.com/groups/gitlab-org/-/epics/9266). -A top-level group can also have one complete +A single top-level group provides insights in your entire organization via a complete [Security Dashboard and Center](../application_security/security_dashboard/index.md), [Vulnerability](../application_security/vulnerability_report/index.md#vulnerability-report) and [Compliance Report](../compliance/compliance_report/index.md), and diff --git a/doc/user/group/manage.md b/doc/user/group/manage.md index 871174d3281..17d4e7fc3df 100644 --- a/doc/user/group/manage.md +++ b/doc/user/group/manage.md @@ -9,10 +9,10 @@ info: To determine the technical writer assigned to the Stage/Group associated w Use groups to manage one or more related projects at the same time. NOTE: -Self-managed customers should create a top-level group so you can see an overview of -your organization. For more information about efforts to create an +For self-managed customers it could be beneficial to create one single top-level group, so you can see an overview of +your entire organization. For more information about efforts to create an organization view of all groups, [see epic 9266](https://gitlab.com/groups/gitlab-org/-/epics/9266). -A top-level group can also have one complete +A single top-level group provides insights in your entire organization via a complete [Security Dashboard and Center](../application_security/security_dashboard/index.md), [Vulnerability](../application_security/vulnerability_report/index.md#vulnerability-report) and [Compliance Report](../compliance/compliance_report/index.md), and |