Labels

Scalability:Frameworks team https://about.gitlab.com/handbook/engineering/infrastructure/team/scalability

Delivery:Orchestration https://about.gitlab.com/handbook/engineering/infrastructure/team/delivery/#deliveryorchestration

https://about.gitlab.com/handbook/engineering/quality/quality-engineering/self-managed-excellence/

Delivery:System https://about.gitlab.com/handbook/engineering/infrastructure/team/delivery/#deliverysystem

Issues and Epics relating to teams, which is a feature owned by the Manage:Spaces group

Work items to clean up or improve existing code that needs attention. This includes follow-ups from code reviews and areas we've identified that could have better implementations. See gitlab-com/content-sites/handbook!10641.

this label is used by automated product operations release pages

Terraform

Issues related to our test suite

A test that failed at least one CI/CD job.

A test that first failed, and then passed when retried in the same CI/CD job.

A test that is slower than the threshold for that test level.

master broken incidents caused by failed e2e pipeline

master broken incidents caused by failed integration tests

master broken incidents caused by failed migration tests

master broken incidents caused by failed system tests

master broken incidents caused by failed unit tests

Issues that describe a QA test plan

This label is used to indicate master-broken incidents where Jest test selection process filters out tests that would have caught an issue.