Labels
Prioritized labels 5
Drag to reorder prioritized labels and change their relative priority.
-
typebugGitLab.orgIssues that report undesirable or incorrect behavior. See https://handbook.gitlab.com/handbook/product/groups/product-analysis/engineering/metrics/#work-type-classification
- Lock on merge
- Issues
- Merge requests
-
maintenancerefactorGitLab.orgIssues related to things that need improvement and that have been left behind due to high velocity of development
Labels 3,576
-
Security HackathonGitLab.orgThis is a label for issues/epics participating in the upcoming Security Hackathon event
-
Security ResearchGitLab.orgIssues owned by the Security Research team. More at https://about.gitlab.com/handbook/engineering/security/security-engineering-and-research/security-research/
-
SecurityPMGitLab.orgApplied to assist the Security Program Manager in tracking issues that cross departments and teams - contact DRI: Will Szabo
-
SecurityReviewCompletedGitLab.orgLabel used for Security Review Framework https://handbook.gitlab.com/handbook/security/product-security/security-review-framework/
-
SecurityReviewIn-ProgressGitLab.orgLabel used for Security Review Framework https://handbook.gitlab.com/handbook/security/product-security/security-review-framework/
-
SecurityReviewInitialTriageGitLab.orgLabel used for Security Review Framework https://handbook.gitlab.com/handbook/security/product-security/security-review-framework/
-
SecurityReviewQueuedGitLab.orgLabel used for Security Review Framework https://handbook.gitlab.com/handbook/security/product-security/security-review-framework/
-
SecurityReviewRequestedGitLab.orgLabel used for Security Review Framework https://handbook.gitlab.com/handbook/security/product-security/security-review-framework/
-
SecurityReviewRiskCalculationGitLab.orgLabel used for Security Review Framework https://handbook.gitlab.com/handbook/security/product-security/security-review-framework/
-
Seeking community contributionsGitLab.orgUncontroversial issues with clear solutions that GitLab is not planning to execute soon. The description should have an Implementation plan second-level heading and a "Weight" value that estimates the complexity. Please mention @gitlab-org/coaches if you have any questions :)
-
Related to the effort to transition self-managed Ultimate trials to cloud licensing. Details in &12173
-
Self-Managed Platformrequest for helpGitLab.orgTemplate for requests for help from the Support team for the Self Managed Platform team