Labels

Unhealthy test issues with between 7 and 10 failed CI/CD jobs reports.

Unhealthy test issues with between 4 and 6 failed CI/CD jobs reports.

Unhealthy test issues with less than 3 failed CI/CD jobs reports.

Tests that fail due to a bug in the test itself, not in the application code

Tests that fail due to a bug in application

Test failure caused by an external dependency

Tests that fail intermittently including those that cause "broken master"

Tests that are under investigation

Tests that have not yet been triaged

Tests that fail because the application was changed without updating the test

Tests that fail because of an issue with an external dependency, e.g., the infrastructure on which the test runs.

Issues related to reduce false positives in security reports

New changes that can be disabled using a feature flag, or existing feature flags that are being removed.

Issues for Feature Management, part of the Release stage of the DevOps lifecycle

potential candidate for Platform Readiness Enablement Process

Issues or MRs related to the first MVC that gives users a foundation of new capabilities that were previously unavailable. Read more at https://handbook.gitlab.com/handbook/product/groups/product-analysis/engineering/metrics/#work-type-classification

Merging a feature into an existing feature for simplification. Read more at https://handbook.gitlab.com/handbook/product/groups/product-analysis/engineering/metrics/#work-type-classification

User-facing improvements that refine the initial MVC to make it more useful and usable. Read more at https://handbook.gitlab.com/handbook/product/groups/product-analysis/engineering/metrics/#work-type-classification

Suggested Reviewer functionality for the AI-powered stage within the Data Science section