Labels

Issues that are under review either before or after deploying by search team

Issue that is ready to be worked on by the search team and should be worked on next

Issues that are ready for development but are not going to be worked on anytime soon until re-prioritized again by the search team

Issue that needs epic, milestone, or does not contain enough information to be worked on yet by the search team

Issue that has been triaged, properly planned out and is ready to be worked on by the search team

Issue that has been planned out but needs further validation before being ready to be worked on by search team

Potential issue that can be planned out and worked on by search team

A label to denote the priority for search team

A label to denote the priority for search team

A label to denote the priority for search team

Any items related to metrics and monitoring for the Code Creation team and Duo Code Suggestions

Applied once community bonus points have been awarded

If you solve this issue, you'll be assigned a community bonus of 100 points

If you solve this issue, you'll be assigned a community bonus of 200 points

If you solve this issue, you'll be assigned a community bonus of 300 points

If you solve this issue, you'll be assigned a community bonus of 500 points

Label used to track work related to improving data integrity across gitlab (as it pertains to project Compass). https://about.gitlab.com/direction/product-intelligence/#resolve-data-integrity-concerns

Issues that are related to competing with another tool or solution identified during Competitive Roadmap Reviews

Features in monday.com

An issue which has been validated, broken down, planned/designed, developed, deployed, but not verified in production. 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