Update and consolidate eng metrics pages

A team's ratio might change over time and different teams may have different ratios. Factors that influence what ratio is appropriate for a given team include the [product category maturity](/handbook/product/categories/), the area of the product they are working in, and the evolving needs of GitLab the business. Teams should review labeling for accuracy and minimize the number of `type::undefined` items. This allows us to review the plans at the group, section, and company level with team members to ensure we appropriately prioritize based on cross-functional perspectives.

For more details on these three work types, please see the section on [work type classification](/handbook/product/groups/product-analysis/engineering/dashboards/#work-type-classification).  The development EM is the DRI to ensure that the merge requests are accurately labeled.

For more details on these three work types, please see the section on [work type classification](/handbook/product/groups/product-analysis/engineering/metrics/#work-type-classification).  The development EM is the DRI to ensure that the merge requests are accurately labeled.

#### Prioritization and DRI by Component

1. [Results](/handbook/values/#results): [Fast growth](https://about.gitlab.com/why-gitlab), [ambitious vision](https://about.gitlab.com/direction/#vision)

1. [Flexible Work Hours](/handbook/company/culture/all-remote/people#those-who-value-flexibility-and-autonomy): Plan your day so you are there for other people & have time for personal interests

1. [Transparency](/handbook/values/#transparency): [Over 2,000 webpages in GitLab handbook](/handbook/about/#count-handbook-pages), [GitLab Unfiltered](https://www.youtube.com/gitlab-unfiltered) YouTube channel

1. [Iteration](/handbook/values/#iteration): [Empower people to be effective & have an impact](/handbook/values/#collaboration), [Merge Request rate](/handbook/product/groups/product-analysis/engineering/dashboards/#merge-request-rate), [We dogfood our own product](/handbook/people-group/using-gitlab-at-gitlab/#introverts-of-gitlab), [Directly responsible individuals](/handbook/people-group/directly-responsible-individuals/)

1. [Iteration](/handbook/values/#iteration): [Empower people to be effective & have an impact](/handbook/values/#collaboration), [We dogfood our own product](/handbook/people-group/using-gitlab-at-gitlab/#introverts-of-gitlab), [Directly responsible individuals](/handbook/people-group/directly-responsible-individuals/)

1. [Diversity, Inclusion & Belonging](/handbook/values/#diversity-inclusion): [A focus on gender parity](/handbook/people-group/people-success-performance-indicators/#diversity---women-at-gitlab),

[Team Member Resource Groups](/handbook/company/culture/inclusion/erg-guide/#definition-of-the-tmg---team-member-groups), [other initiatives](/handbook/company/culture/inclusion#what-we-are-doing-with-diversity-inclusion--belonging)

1. [Collaboration](/handbook/values/#collaboration): [Kindness](/handbook/values/#kindness), [saying thanks](/handbook/values/#say-thanks), [intentionally organize informal communication](/handbook/company/culture/all-remote/informal-communication), [no ego](/handbook/values/#no-ego)

#### Mechanics

- The team reviewus [this dashboard](/handbook/product/groups/product-analysis/engineering/dashboards/#mr-types-dashboard) which shows the distribution of MRs that are bugs, maintenance, and features to ensure the team's efforts are properly aligned to our target prioritization ratio (60% features / 30% maintenance / 10% bugs).

- The team reviewus [this dashboard](/handbook/product/groups/product-analysis/engineering/dashboards/#dashboards) which shows the distribution of MRs that are bugs, maintenance, and features to ensure the team's efforts are properly aligned to our target prioritization ratio (60% features / 30% maintenance / 10% bugs).

- The team uses [this prioritization board](https://gitlab.com/gitlab-org/gitlab/-/boards/4416231?label_name%5B%5D=group%3A%3Autilization) to order our top features, bugs, maintenance, and [System Usability Scale (SUS)](/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#ux-bugs) impacting issues.

- For a quick view and controls on bugs by priority, [this board](https://gitlab.com/groups/gitlab-org/-/boards/2874336?label_name[]=group%3A%3Autilization&label_name[]=type%3A%3Abug) can be used. More detailed information on bugs, including backlog and open rate, both of which are factors in determining their desired bug percentage for the upcoming milestone, is shown in this [dashboard](https://10az.online.tableau.com/t/gitlab/views/OpenBugAgeOBA/BugPrioritizationDashboard) (select Utilization from filters).

- The team collaborates on a prioritization issue that documents and discusses our current prioritization scheme.

### Labels in gitlab-org group

Stage groups use [type labels](/handbook/product/groups/product-analysis/engineering/dashboards/#data-classification) to label merge requests in projects in the `gitlab-org` group.

Stage groups use [type labels](/handbook/product/groups/product-analysis/engineering/metrics/#work-type-classification) to label merge requests in projects in the `gitlab-org` group.

If you need a stage group to perform work, it is best to apply the relevant stage group label when the issue is created.

## Issue Trackers

### `product_community_contribution_mrs`

Merge requests with ~"Community contribution" label, opened in

[projects that are part of the product](/handbook/product/groups/product-analysis/engineering/dashboards/#projects-that-are-part-of-the-product).

[projects that are part of the product](/handbook/product/groups/product-analysis/engineering/metrics/#projects-that-are-part-of-the-product).

The results include MR type, MR age, MR labels, MR stage, MR group, MR section.