Labels
Prioritized labels 9
Drag to reorder prioritized labels and change their relative priority.
-
frontendGitLab.orgIssues for the Frontend team. Covers everything related to the way GitLab behaves (and, to an extent, looks) inside your browser.
-
golangGitLab.orgIssues for Ruby teams that require some knowledge of Go, because they may require changes in Gitaly, Workhorse, etc
-
workflowready for developmentGitLab.orgIssue has been broken down and prioritized by PM for development https://handbook.gitlab.com/handbook/product-development-flow/#description-4
-
workflowin devGitLab.orgIssues that are actively being worked on by a developer https://handbook.gitlab.com/handbook/product-development-flow/#description-5
-
workflowin reviewGitLab.orgIssues that are undergoing code review by the development team and/or undergoing design review by the UX team https://handbook.gitlab.com/handbook/product-development-flow/#description-5
-
workflowverificationGitLab.orgEverything has been merged, waiting for verification after a deploy https://handbook.gitlab.com/handbook/product-development-flow/#description-5
Labels 3,492
-
test-selection-gapjestGitLab.orgThis label is used to indicate master-broken incidents where Jest test selection process filters out tests that would have caught an issue.
-
test-selection-gaprspecGitLab.orgThis label is used to indicate master-broken incidents where RSpec test selection process filters out tests that would have caught an issue.
-
themeca efficient vuln remediationGitLab.orgAny issue or epic relating to features/enhancements that will enable users to better perform their remediation tasks for vulnerabilities. This can include prioritization methods or any mechanism that makes AppSec's job easier.
-
themeca scanner coverageGitLab.orgRoadmap theme for Composition Analysis, focusing on expanding scanner coverage enhancements. This can include updates to existing functionality as well as supporting new languages / frameworks / package managers.