Update data category to operational
What does this MR do and why?
Updated the data category on usage_activity_by_stage_monthly.package.projects_with_packages
to Operational
from Optional
per @nk312 of Customer Success team. Reference: https://gitlab.com/gitlab-com/sales-team/field-operations/customer-success-operations/-/issues/1034#note_896619208
Business justification for moving metric to Operational category
To support customer success services for us to build out maturity models for the Package stage
- Why does CS need this: To gain an understanding of the use of Package, explicitly looking at the relationship between how many active projects use packages. With an existing metric of the # of projects, this will help us understand the depth of package penetration into the instance or namespace
- How will this be used: With running analytics on active package projects vs. how many projects are not actively using packages?
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.