Absorb the Code Analytics category into Value Stream Management and DevOps Adoption

Overview

Code Analytics is a product category that is at Minimal maturity level. It is described in the direction page as a deep dive into the Code stage of Value Stream Analytics to find bottlenecks. ~"Category:Value Stream Management" already provides high-level insight into the time that workflow items spend in the code stage relative to other stages of the software development life cycle and allows users to drill in and identify bottlenecks. Value Stream Analytics will link to other key parts of the UI so that users can dive deeper. Additionally, DevOps Reports will show usage metrics for features in the Create stage and how usage correlates to performance.

Secondly, there is no clear maturity plan or roadmap for this product category and it has been sitting stale since its inception.

Proposal

Given the duplication with existing product categories, Value Stream Management and DevOps Reports, and the lack of maturity plan, direction, and roadmap, I don't think it is worth the overhead of maintaining a separate product category for code analytics and recommend that this category be absorbed into Value Stream Management and DevOps Reports.

More background

For more background on this decision, see the discussion in the linked issue.

Approvals

Merge requests with changes to stages and groups and significant changes to categories need to be created, approved, and/or merged by each of the below:

• Chief Product Officer @sfwgitlab
• VP of Product @adawar
• The Product Director relevant to the stage group(s) @david
• The Engineering Director relevant to the stage group(s) @timzallmann
• Director of Product Design @vkarnes
• CEO @sytses

The following people need to be on the merge request so they stay informed:

• Chief Technology Officer @edjdev
• Vice President of Development @clefelhocz1
• Director of Quality @meks
• Vice President of User Experience @clenneville
• The Product Marketing Manager relevant to the stage group(s) @cfoster3

Relates to gitlab-org/gitlab#322677 (closed)

data/release_posts/unreleased/admin-instancelevel-page-list-project-overrides-table.yml

+---
+features:
+  secondary:
+  - name: "View projects that use custom integration settings"
+    available_in: [core, premium, ultimate]
+    gitlab_com: true
+    documentation_link: 'https://docs.gitlab.com/ee/user/admin_area/settings/project_integration_management.html#view-projects-that-override-the-default-settings'
+    image_url: '/images/unreleased/integrations_project_settings.png'
+    reporter: mushakov
+    stage: create
+    categories:
+    - Integrations
+    issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/218252'
+    description: |
+      In this release, we are making the management of project integration configuration much easier! GitLab administrators can now see a list of projects that are not using the default integration configuration. This functionality helps administrators ensure that projects have the right data from integrated systems.