- Gather time to resolve severity::1/severity::2 issues in an automated fashion with ability to filter only customer affecting defects. => **Done**[Create Visualization for mean time to resolve severity::1-severity::2 functional defects](https://gitlab.com/gitlab-org/gitlab-insights/issues/109)
- Provide missed SLO visibility of priority::1/priority::2 bugs to Product and Engineering Managers to maintain SLO threshold of priority::1/priority::2 bugs. => **Done**[Remove SLO detection for priority::3](https://gitlab.com/gitlab-org/quality/triage-ops/issues/230)[Remove missed-slo from priority::3/priority::4 bugs](https://gitlab.com/gitlab-org/quality/triage-ops/issues/238)
- Provide visibility into completed deliverables vs non-deliverables. => **Done**[Show completed deliverables per milestone](https://gitlab.com/gitlab-org/gitlab-insights/issues/119)
- An effective iteration to the current [stage group triage package/report](/handbook/engineering/infrastructure/engineering-productivity/triage-operations/#team-reports) to highlight customer affecting defects. => **Done**[Triage package v2.0](https://gitlab.com/gitlab-org/quality/triage-ops/issues/186)
- An effective iteration to the current [stage group triage package/report](/handbook/engineering/infrastructure-platforms/developer-experience/triage-operations/#team-reports) to highlight customer affecting defects. => **Done**[Triage package v2.0](https://gitlab.com/gitlab-org/quality/triage-ops/issues/186)
- Training for Engineering Managers and Product Managers to use Priority and Severity label effectively. => **Done**[Triage training recording for EMs and PMs](https://gitlab.com/gitlab-org/quality/team-tasks/issues/148) now linked to the triage-operations landing page.
- Training for Engineering Managers on KPIs and interventions they can make. => **Done** Reviewed current iteration, material is adequate.
@@ -113,7 +113,7 @@ These items must be triaged continuously throughout the milestone which means th
#### Responsibilities - Maintainership
1. Work with community contributors to help drive [their merge requests](https://gitlab.com/groups/gitlab-org/-/merge_requests?scope=all&state=opened&label_name[]=group%3A%3Acomposition%20analysis&label_name[]=Community%20contribution) to completion (more information on [community contributions triaging process](/handbook/engineering/infrastructure/engineering-productivity/merge-request-triage/)).
1. Work with community contributors to help drive [their merge requests](https://gitlab.com/groups/gitlab-org/-/merge_requests?scope=all&state=opened&label_name[]=group%3A%3Acomposition%20analysis&label_name[]=Community%20contribution) to completion (more information on [community contributions triaging process](/handbook/engineering/infrastructure-platforms/developer-experience/merge-request-triage/)).
1. Run the [License Alias Generator](https://gitlab.com/gitlab-org/security-products/license-db/license-alias-generator/-/tree/main?ref_type=heads) tool to update the list of [known alias](https://gitlab.com/gitlab-org/security-products/license-db/license-processor/-/blob/main/data/aliases.go?ref_type=heads). You can find instructions [here](https://gitlab.com/gitlab-org/security-products/license-db/license-alias-generator/-/tree/main?ref_type=heads#workflow). This action should be performed once during a milestone.
1. Check for new versions of languages or package managers that we support, or deprecation / removal of support for the same and notify Engineering Manager and Product Manager via issue.
1. Check for new versions of our dependencies (not related to security):
@@ -424,7 +424,7 @@ Within the Environments group we use the following processes and best practices
1. We ensure each MR is accompanied with meaningful unit tests and integration tests.
1. For each major feature we develop and maintain End to End tests that run nightly and confirm no regressions have been introduced to critical paths.
1. On a weekly basis, we review our [Triage report](/handbook/engineering/infrastructure/engineering-productivity/triage-operations/#triage-reports) for bugs and regressions and take the appropriate action.
1. On a weekly basis, we review our [Triage report](/handbook/engineering/infrastructure-platforms/developer-experience/triage-operations/#triage-reports) for bugs and regressions and take the appropriate action.
1. We review the [quality dashboard](https://10az.online.tableau.com/t/gitlab/views/OpenBugAgeOBA/OpenBugAgeOBADashboard) each milestone to track our long term progress at improving quality.
@@ -245,7 +245,7 @@ The Verify Technical Discussions are automatically recorded and added to [Google
## Weekly Triage Reports
The Product Manager, Engineering Manager(s), and Designer for each group are responsible for triaging and scheduling [feature proposals and bugs as part of the Weekly Triage Report](/handbook/engineering/infrastructure/engineering-productivity/triage-operations/#group-level-bugs-features-and-deferred-ux). Product Managers schedule issues by assigning them to a Milestone or the Backlog. For bug triage, Engineering Managers and Product Managers work together to ensure that the correct `severity` and `priority` labels have been applied. Since [Product Managers are the DRIs for prioritization](/handbook/product-development/how-we-work/issue-triage/#priority), they will validate and/or apply the initial `priority` label to bugs. Engineering Managers are responsible for adding or updating the `severity` labels for bugs listed in the triage report, and to help Product Management with understanding the criticality and technical feasibility of the bug, as needed.
The Product Manager, Engineering Manager(s), and Designer for each group are responsible for triaging and scheduling [feature proposals and bugs as part of the Weekly Triage Report](/handbook/engineering/infrastructure-platforms/developer-experience/triage-operations/#group-level-bugs-features-and-deferred-ux). Product Managers schedule issues by assigning them to a Milestone or the Backlog. For bug triage, Engineering Managers and Product Managers work together to ensure that the correct `severity` and `priority` labels have been applied. Since [Product Managers are the DRIs for prioritization](/handbook/product-development/how-we-work/issue-triage/#priority), they will validate and/or apply the initial `priority` label to bugs. Engineering Managers are responsible for adding or updating the `severity` labels for bugs listed in the triage report, and to help Product Management with understanding the criticality and technical feasibility of the bug, as needed.
While SLOs for resolving bugs are tied to severities, it is up to Product Management to set priorities for the group with an appropriate target resolution time. For example, criteria such as the volume of `severity::2` level bugs may make it appropriate for the Product Manager to adjust the priority accordingly to reflect the expected time to resolution.
