Commit a3df5cde authored by Kai Armstrong's avatar Kai Armstrong Committed by James Ramsay
Browse files

January Code Review PI Updates

parent b37e0418
......@@ -557,7 +557,7 @@
base_path: "/handbook/product/performance-indicators/"
definition: This is defined as users who perform one or more of the following actions in
a merge request - create, merge, or close a Merge Request.
target: Undefined - Expect to set baseline in January 2021
target: Our target growth rate is 3% higher than the previous month for SMAU, and 4% for Paid SMAU.
org: Dev Section
section: dev
stage: create
......@@ -568,10 +568,11 @@
is_primary: true
is_key: false
health:
level: 0
level: 2
reasons:
- Target - Target is undefined as instances continue to upgrade from when metric tracking began. This looks to be stabilizing, but one more month should clarify this for us.
- Insight - Code Review appears to have about 50% of the MAU of Source Code. This is being investigated in [#1797](https://gitlab.com/gitlab-com/Product/-/issues/1797). Most recent insights are in [this comment](https://gitlab.com/gitlab-com/Product/-/issues/1797#note_458403616).
- Target - This aligns with our current understanding that Code Review is about 50% of the MAU of the stage metric and continuing to maintain that difference.
- Insight - Continued investigation in to the drop-off between SCM and Code Review is being investigated by the data team in [data issue 7468](https://gitlab.com/gitlab-data/analytics/-/issues/7468).
- Insight - Paid users of Code Review make up about one-third of total Code Review users.
- Improvement - Support for [custom commit messages when applying a suggested change](https://gitlab.com/gitlab-org/gitlab/-/issues/25381) will allow more teams with strict commit message guidelines to adopt this feature and maintain conformity with the project.
- Improvement - Add [reviewers to merge request](https://gitlab.com/groups/gitlab-org/-/epics/1823) to better signal who is responsible for reviewing compared to being assigned without a clear action to take.
implementation:
......@@ -587,11 +588,36 @@
embed: v2
sisense_data_secondary:
chart: 9601815
dashboard: 664109
dashboard: 10624715
embed: v2
urls:
- https://app.periscopedata.com/app/gitlab/526749/Create---Code-Review-category-dashboard
 
- name: Create:Code Review - Other - % of MAU using Merge Requests
base_page: "/handbook/product/performance-indicators/"
definition:
target: TBD - Primarily this metric is used for monitoring adoption on a broad scale and remains consistent.
org: Dev Section
section: dev
stage: create
group: code_review
public: true
pi_type: Other
product_analytics_type: Both
is_primary: false
is_key: false
health:
level: 0
reasons:
- Target - this metric is primarily monitored to remain at a consistent level.
implementation:
status: Complete
metric_name: merge_requests_users
sisense_data:
chart: 9601815
dashboard: 664109
embed: v2
- name: Create:Gitaly - Other - Availability
base_path: "/handbook/product/performance-indicators/"
definition: Percentage of time during which Gitaly is fully operational and providing
......
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