Labels
Prioritized labels 7
Drag to reorder prioritized labels and change their relative priority.
-
securityGitLab.orgIssues related to the security of GitLab or its dependencies. Please report vulnerabilities responsibly per https://about.gitlab.com/security/disclosure/
-
customerGitLab.orgIssues that were reported by Enterprise Edition subscribers. This label should be accompanied by either the 'bug' or 'feature proposal' label
-
customer+GitLab.orgFeatures and bugs reported by large enterprise customers. This label is in use by the product org, please post in #product Slack channel if you have questions.
-
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
-
directionGitLab.orgIssues for important features that are on our roadmap: https://about.gitlab.com/direction/
Labels 3,440
-
Alliances - OracleGitLab.orgLabel for all Oracle product issues pertaining to alliances and technology partnership
-
Alliances - StackOverflowGitLab.orgLabel for all StackOverflow issues pertaining to alliances and technology partnership
-
Identifies items that serve towards our product direction: "Broaden instrumentation coverage - Cover all use cases"
-
Analytics InstrumentationData QualityGitLab.orgIdentifies items that serve towards our product direction "Data quality: Ensure the accuracy and reliability of the data we collect for trusted decision-making. Adhering to legal and privacy policies to ensure compliance and protect user privacy"
-
Analytics InstrumentationData to InsightsGitLab.orgIdentifies items that serve towards our product direction: "Data to Insights: Ensure the data we collect can be effectively transformed into actionable insights by our internal teams and customers"
-
Identifies items that serve towards our product direction: "Deepen Instrumentation adoption/Instrumentation coverage: Ensure all our categories have instrumentation"
-
Identifies items that serve towards our product direction: "Easy instrumentation: Providing infrastructure and tools that enable teams to efficiently instrument with minimal support"
-
Issues that serve to improve engineering effectiveness and reducing tech debt but do not directly serve any product goal.
-
AppSecPriority1GitLab.orgAppSec top priority work that must be completed for the end of the planned milestone.
-
AppSecPriority2GitLab.orgAppSec work priority that is important and is prioritized as soon as all ~"AppSecPriority::1" work is completed. ~"AppSecPriority::2" work will become ~"AppSecPriority::1"` on the next milestone.
-
AppSecPriority3GitLab.orgAppSec work priority that is less important and is prioritized as soon as all ~"AppSecPriority::2" work is completed. ~"AppSecPriority::3" will be evaluated during Milestones Planning Sessions and may become ~"AppSecPriority::2" for the next milestone.
-
AppSecWeightNeeds RefinementGitLab.orgIssue is overly complex, needs to be broken down into smaller issues
-
AppSecWeightXLargeGitLab.org~5-10 days: Very complex, requires major portion of a milestone to resolve