Labels

plans, methods, or series of maneuvers or stratagems for obtaining specific goals or results

This label is used for requesting engineering support for strategy programs

To signify a Support Ops issue/MR is a change level 1

To signify a Support Ops issue/MR is a change level 2

To signify a Support Ops issue/MR is a change level 3

To signify a Support Ops issue/MR is a change level 4

Access Request provisioning completed

Access Request pending provisioning from Support

Issues related to team management, team infrastructure and general team tasks

Customer Support department. https://handbook.gitlab.com/handbook/support/

https://about.gitlab.com/handbook/engineering/infrastructure/team/reliability/database-reliability.html

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

Issues belonging to the Delivery:Orchestration team. See https://about.gitlab.com/handbook/engineering/infrastructure/team/delivery/#deliveryorchestration

Used to track epics for departmental updates, for more information see https://internal.gitlab.com/handbook/security/product_security/security-platforms-architecture/product-security-reporting/

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

The Reliability Engineering team is comprised of Site Reliability Engineers (SREs). All our work is tagged with this label. See https://about.gitlab.com/handbook/engineering/infrastructure/team/reliability.

https://about.gitlab.com/handbook/engineering/infrastructure/team/reliability/observability.html