Labels

Support requests for the Development Tooling team, covering issues, enhancements, or questions related to tools, processes, and workflows within the Development Tooling scope.

A security issue which has been validated, broken down, planned/designed, developed and is waiting for a security release to be deployed. This label is being used as part of an experiment and should not be manually added/removed. See gitlab-org/developer-relations/contributor-success/team-task#382

An issue which has been validated, broken down, planned/designed, but development is blocked until another issue is complete. This label is being used as part of an experiment and should not be manually added/removed. See gitlab-org/developer-relations/contributor-success/team-task#382

An issue which has been validated, broken down, planned/designed, developed and is in review. This label is being used as part of an experiment and should not be manually added/removed. See gitlab-org/developer-relations/contributor-success/team-task#382

An issue which has been validated, broken down/planned/designed and is ready for development to begin. This label is being used as part of an experiment and should not be manually added/removed. See gitlab-org/developer-relations/contributor-success/team-task#382

An issue which has been validated, broken down/planned/designed and is in development. This label is being used as part of an experiment and should not be manually added/removed. See gitlab-org/developer-relations/contributor-success/team-task#382

No AI usage – the work was done entirely by the author without AI tools

Minor AI assistance – AI used for small tasks like autocompletion, typo fixes, or quick lookups

Moderate AI assistance – AI used to help draft portions of code, tests, or documentation alongside manual work

Significant AI assistance – majority of the work was generated or guided by AI, with human review and refinement

Fully AI-driven – the entire change was generated by AI with minimal human editing

AI-powered stage part of the Data Science section

Issues for the Analytics stage of the DevOps lifecycle

Issues for the Anti-Abuse stage of the DevOps lifecycle (e.g. Anti-Abuse)

https://handbook.gitlab.com/handbook/product/categories/#application-security-testing-stage (e.g. SAST, DAST, Secret Detection, Dependency Scanning, Vulnerability Database)

[DEPRECATED] should use devops::deploy now. Issues for the Configure stage of the DevOps lifecycle (e.g. Auto DevOps , Kubernetes Configuration, ChatOps, Serverless, PaaS)

Issues for the Create stage of the DevOps lifecycle (e.g. Source Code Management, Design Management, Web IDE, Code Review, Gitter)