Labels
Prioritized labels 47
Drag to reorder prioritized labels and change their relative priority.
- Architecture Evolution BlueprintGitLab.orgChanges to Architecture Evolution Blueprints described at https://about.gitlab.com/handbook/engineering/architecture/workflow/
- groupcontainer registryGitLab.orgIssues belonging to the Container Registry group of the Package stage of the DevOps lifecycle. See https://about.gitlab.com/handbook/product/categories/#container-registry-group
- quick winfirst-time contributorGitLab.orgQuick win issues that are ideal for first-time community contributors to work on
- VerifyP1GitLab.orgIssues related to current milestone's top product priorities for the Pipeline Execution group in the Verify stage
- complexitylowGitLab.orgIssue with low technical complexity. Complexity does not describe the time it will likely require to address the issue, but rather the familiarity required to address it. This label is only intended as a guideline to hint to individuals how involved the issue will likely be.
- VerifyP2GitLab.orgIssues related to next milestone's top product priorities for the Pipeline Execution group in the Verify stage
- complexitymediumGitLab.orgIssue with medium technical complexity. Complexity does not describe the time it will likely require to address the issue, but rather the familiarity required to address it. This label is only intended as a guideline to hint to individuals how involved the issue will likely be.
- workflowin devGitLab.orgIssues that are actively being worked on by a developer https://handbook.gitlab.com/handbook/product-development-flow/#description-5
- VerifyP3GitLab.orgIssues related to future milestone's top product priorities for the Pipeline Execution group in the Verify stage
- complexityhighGitLab.orgIssue with high technical complexity. Complexity does not describe the time it will likely require to address the issue, but rather the familiarity required to address it. This label is only intended as a guideline to hint to individuals how involved the issue will likely be.
- workflowblockedGitLab.orgIssues that are blocked until another issue has been completed https://handbook.gitlab.com/handbook/product-development-flow/#description-5
- Category:Global SearchGitLab.orgIssues related to search using the search field in the top navigation bar
- workflowcompleteGitLab.orgApplied after all MRs have merged and the issue has been verified if necessary https://handbook.gitlab.com/handbook/product-development-flow/#build-phase-3-launch
- 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
- Model ExperimentsGitLab.orgModel Experiments allows Data Scientists to track candidates for their machine learning models
- workflowrefinementGitLab.orgIssues that need further input from team members in order for it to be "workflow::ready for development" https://handbook.gitlab.com/handbook/product-development-flow/#build-phase-1-plan
- workflowready for reviewGitLab.orgMerge requests which are ready to be reviewed and can be reviewed by any team-member with sufficient knowledge in the given area. For reviewing the merge request just assign to yourself and remove this label.
- workflowsolution validationGitLab.orgWorkflow label for validating that the proposed solution meets user needs https://handbook.gitlab.com/handbook/product-development-flow/#validation-phase-4-solution-validation
- modular_monolithGitLab.org / GitLabIssues related to the effort of having a Modular Monolith and #modular_monolith Slack channel discussions
- workflowfeature-flaggedGitLab.orgEnabled through a separate feature flag rollout issue. https://handbook.gitlab.com/handbook/engineering/development/ops/verify/pipeline-execution/#workflow
- Category:Code SearchGitLab.orgCode Search Category is part of Global Search that focuses on searching through Code Across Repositories
- quad-planningcomplete-no-actionGitLab.orgIssue has gone through Quad Planning process (PM,Dev,UX,QE) and does not require any additional action
- StORMIntakeGitLab.orgLabel to communicate potential security operational risks to the Security Risk Team
- StORMNeeds Additional InformationGitLab.orgAdditional information is required to support the Security Risk Team's StORM Risk Assessment
- CI persistenceGitLab.orgIssues related to Persistence (workspaces, caching). Does not include artifacts, which is its own label
- StORMOut of ScopeGitLab.orgThe Security Risk Team performed a StORM Risk Assessment and determined that the potential risk identified is out of scope for the StORM program because it is not considered an operational security risk.
- StORMUnder AssessmentGitLab.orgLabel used to note the Security Risk Team is currently assessing a potential risk
- Risk and Field SecurityGitLab.orgThis label is for things related to the Risk and Field Security team
- priority1GitLab.orgWe will address this as soon as possible regardless of limit on our team capacity. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority
- priority2GitLab.orgWe will address this soon and will provide capacity from our team for it in the next few releases. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority
- priority3GitLab.orgWe want to address this but may have other higher priority items. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority
- priority4GitLab.orgWe don't have visibility when this will be addressed. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority
- UXGitLab.orgIssues or MRs that introduce user-facing changes or impact the user experience. Applying this label to issues will signal a need for a designer.
Labels 4,273
- Alliances - StackOverflowGitLab.orgLabel for all StackOverflow issues pertaining to alliances and technology partnership
- AlphaGitLab.org / GitLabAlpha release of a large, complex feature that needs to be tested before we are confident it can scale, support, and maintain in production use.
- 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.