summaryrefslogtreecommitdiff
path: root/doc/user/analytics
diff options
context:
space:
mode:
Diffstat (limited to 'doc/user/analytics')
-rw-r--r--doc/user/analytics/cycle_analytics.md8
-rw-r--r--doc/user/analytics/index.md13
2 files changed, 10 insertions, 11 deletions
diff --git a/doc/user/analytics/cycle_analytics.md b/doc/user/analytics/cycle_analytics.md
index b7389c8689d..377af433342 100644
--- a/doc/user/analytics/cycle_analytics.md
+++ b/doc/user/analytics/cycle_analytics.md
@@ -1,7 +1,10 @@
# Cycle Analytics
> - Introduced prior to GitLab 12.2 at the project level.
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/12077) in [GitLab Premium](https://about.gitlab.com/pricing/) 12.2 at the group level (enabled by feature flag `analytics`).
+> - [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/12077) in [GitLab Premium](https://about.gitlab.com/pricing/) 12.2 at the group level.
+
+NOTE: **Note:**
+As of GitLab 12.3 this feature is enabled by the `cycle_analytics` feature flag.
Cycle Analytics measures the time spent to go from an [idea to production] - also known
as cycle time - for each of your projects. Cycle Analytics displays the median time for an idea to
@@ -24,9 +27,6 @@ Cycle Analytics is available:
In the future, multiple groups will be selectable which will effectively make this an
instance-level feature.
- NOTE: **Note:**
- Requires the [analytics workspace](index.md) to be enabled.
-
- At the project level via **Project > Cycle Analytics**.
There are seven stages that are tracked as part of the Cycle Analytics calculations.
diff --git a/doc/user/analytics/index.md b/doc/user/analytics/index.md
index ec719c0b4a1..ba2735dc324 100644
--- a/doc/user/analytics/index.md
+++ b/doc/user/analytics/index.md
@@ -1,22 +1,21 @@
# Analytics workspace
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/12077) in GitLab 12.2 (enabled using `analytics` feature flag).
+> [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/12077) in GitLab 12.2.
The Analytics workspace will make it possible to aggregate analytics across
GitLab, so that users can view information across multiple projects and groups
in one place.
-To access the centralized analytics workspace:
-
-1. Ensure it's enabled. Requires a GitLab administrator to enable it with the `analytics` feature
- flag.
-1. Once enabled, click on **Analytics** from the top navigation bar.
+To access the centralized analytics workspace, click on **Analytics** from the top navigation bar.
## Available analytics
From the centralized analytics workspace, the following analytics are available:
-- [Cycle Analytics](cycle_analytics.md).
+- [Cycle Analytics](cycle_analytics.md):
+
+1. Requires a GitLab administrator to enable it with the `cycle_analytics` feature flag.
+1. Once enabled, click on **Analytics** and then **Cycle Analytics** from the top navigation bar.
NOTE: **Note:**
Project-level Cycle Analytics are still available at a project's **Project > Cycle Analytics**.