Commit 628f1409 authored by Haris Delalić's avatar Haris Delalić 🖖
Browse files

Update Manage:Import GMAU PI for Feb 2021

parent 298f2e02
......@@ -178,7 +178,7 @@
- name: Manage:Import - GMAU - MAU importing
base_path: "/handbook/product/performance-indicators/"
definition: A monthly count of the unique number of users performing an import.
definition: A monthly count of the unique number of users performing an import
target: TBD - See Health section below for details
org: Dev Section
section: dev
......@@ -193,14 +193,14 @@
level: 0
reasons:
- No target defined yet.
- Target will be defined after the [metric instrumentation](https://gitlab.com/gitlab-org/gitlab/-/issues/297431) is implemented.
- Improvement - Reducing friction for GitLab-to-GitLab migrations - The [MVC for the Group Migration feature](https://gitlab.com/groups/gitlab-org/-/epics/4374) which allows a much easier migration of an entire GitLab group will be delivered in `13.8`.
- Target will be defined after the [metric instrumentation](https://gitlab.com/gitlab-org/gitlab/-/issues/283175) is implemented and we get a baseline of data.
- Improvement - Reducing friction for GitLab-to-GitLab migrations - The [MVC for the Group Migration feature](https://gitlab.com/groups/gitlab-org/-/epics/4374) was enabled in production in `13.9`. This feature will enable a much easier migration of an entire GitLab group from one instance to another.
implementation:
status: Instrumentation
status: Dashboard
reasons:
- Instrumentation [originally completed](https://gitlab.com/gitlab-org/gitlab/-/issues/235424) in `13.5` looked incorrect (numbers very high) when reviewed in November. [Investigation](https://gitlab.com/gitlab-org/gitlab/-/issues/281604) of the data concluded that the original instrumentation was not implemented correctly and a [new instrumentation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/297431) was created to fix the metric.
- Due to the current constraint in the bandwidth of the Manage:Import Backend Engineering team and recent increased volume of escalations from Support and the ProServ team, the new instrumentation issue is expected at the earliest in `13.8`.
metric_name: unique_users_all_imports (WIP - https://gitlab.com/gitlab-org/gitlab/-/issues/297431)
- Instrumentation has been [implemented](https://gitlab.com/gitlab-org/gitlab/-/issues/283175) in `13.9`.
- Dashboard [update](https://gitlab.com/gitlab-data/analytics/-/issues/4244) is in progress.
metric_name: unique_users_all_imports
- name: Manage:Import - Other - Share of New Projects Imported
base_path: "/handbook/product/performance-indicators/"
......@@ -221,7 +221,7 @@
reasons:
- No target defined yet.
- Target will be defined once the dashboard is [updated](https://gitlab.com/gitlab-data/analytics/-/issues/4244) with the improved metric (for both Saas and self-managed).
- Improvement - Reducing friction for GitLab-to-GitLab migrations - The [MVC for the Group Migration feature](https://gitlab.com/groups/gitlab-org/-/epics/4374) which allows a much easier migration of an entire GitLab group will be delivered in `13.8`.
- Improvement - Reducing friction for GitLab-to-GitLab migrations - The [MVC for the Group Migration feature](https://gitlab.com/groups/gitlab-org/-/epics/4374) was enabled in production in `13.9`. This feature will enable a much easier migration of an entire GitLab group from one instance to another.
implementation:
status: Dashboard
reasons:
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment