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,466
-
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.
-
AppSecResolutionSLAat-riskGitLab.orgApplied when MR review has been in progress for 1 day. Work is at risk of breaching the 3-day resolution SLA.
-
AppSecResolutionSLAbreachedGitLab.orgApplied when MR review exceeds 3 days. The resolution SLA has been breached and requires immediate attention.
-
AppSecResolutionSLAcompleted-within-slaGitLab.orgApplied when AppSec completes the MR review within the 3-day SLA. Indicates successful on-time resolution.
-
AppSecResolutionSLAnear-breachGitLab.orgApplied when MR review has been in progress for 2 days. Resolution SLA will breach within 24 hours.