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

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

Issues for the Delivery team: https://about.gitlab.com/handbook/engineering/infrastructure/team/delivery/

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

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

Environment Automation Team label used to identify issues, MRs, epics owned by the Environment Automation Team in GitLab Dedicated Group

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

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

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

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

For work being performed by the Product Security Engineering Team: https://handbook.gitlab.com/handbook/security/security-engineering/product-security-engineering/