Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.
  • groupfoundations
    GitLab.org
    Group covering our design system (Pajamas) and foundational Frontend experiences
  • groupglobal search
    GitLab.org
    Issues belonging to the Global Search group of the Core Platform stage of the DevOps lifecycle.
  • Issues related to search using the search field in the top navigation bar
  • Model Experiments
    GitLab.org
    Model Experiments allows Data Scientists to track candidates for their machine learning models
  • groupauthorization
    GitLab.org
    Issues belonging to the Authorization group of the Govern stage of the DevOps lifecycle, https://about.gitlab.com/handbook/product/categories/#authorization-group
  • groupobservability
    GitLab.org
    Issues belonging to the Observability group of the Analyze stage, for product category Error Tracking. See https://about.gitlab.com/handbook/product/categories/#observability-group
  • modular_monolith
    GitLab.org / GitLab
    Issues related to the effort of having a Modular Monolith and #modular_monolith Slack channel discussions
  • Indicates that the structure.sql can be changed without introducing migrations
  • Code Search Category is part of Global Search that focuses on searching through Code Across Repositories
  • Changes to Architecture Evolution Blueprints described at https://about.gitlab.com/handbook/engineering/architecture/workflow/
  • Secure: Issues being worked on by the Secure Analyzer Frontend Team
  • SaaS services for the US Public Sector
  • Issue has gone through Quad Planning process (PM,Dev,UX,QE) and does not require any additional action
  • SaaS services for the US Public Sector
  • StORMIntake
    GitLab.org
    Label to communicate potential security operational risks to the Security Risk Team
  • Additional information is required to support the Security Risk Team's StORM Risk Assessment
  • CI persistence
    GitLab.org
    Issues related to Persistence (workspaces, caching). Does not include artifacts, which is its own label
  • StORMOut of Scope
    GitLab.org
    The 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.
  • Label used to note the Security Risk Team is currently assessing a potential risk
  • milestonep1
    GitLab.org
    Priority 1 for the assigned milestone.
  • This label is for things related to the Risk and Field Security team
  • milestonep2
    GitLab.org
    Priority 2 for the assigned milestone.
  • milestonep3
    GitLab.org
    Priority 3 for the assigned milestone.
  • milestonep4
    GitLab.org
    Priority 4 for the assigned milestone.
  • Deliverable
    GitLab.org
    Issues scheduled for the current milestone.
  • CI rules
    GitLab.org
    Issues related to CI rules or linting
  • priority1
    GitLab.org
    We will address this as soon as possible regardless of limit on our team capacity. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
  • priority2
    GitLab.org
    We will address this soon and will provide capacity from our team for it in the next few releases. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
  • priority3
    GitLab.org
    We want to address this but may have other higher priority items. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
  • priority4
    GitLab.org
    We don't have visibility when this will be addressed. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
  • VerifyP1
    GitLab.org
    Issues related to current milestone's top product priorities for the Pipeline Execution group in the Verify stage
  • VerifyP2
    GitLab.org
    Issues related to next milestone's top product priorities for the Pipeline Execution group in the Verify stage
  • VerifyP3
    GitLab.org
    Issues related to future milestone's top product priorities for the Pipeline Execution group in the Verify stage
  • UX
    GitLab.org
    Issues or MRs that introduce user-facing changes or impact the user experience. Applying this label to issues will signal a need for a designer.
  • Other labels

  • ~jks-competitive
    GitLab.org / GitLab
  • workhorse
    GitLab.org
    Issues on both the GitLab Workhorse and GitLab CE projects
  • Successfully completed the current version (experimental or beta) and promoted to the next version (beta or GA). See https://docs.gitlab.com/ee/policy/alpha-beta-support.html
  • Everything has been merged, waiting for verification after a deploy.
  • Issues in a backlog of potential validation opportunities. This label is part of the product development flow https://about.gitlab.com/handbook/product-development-flow/#workflow-summary
  • workflowstart
    GitLab.org
    The entry point for workflow scoped labels. From here, Issues will either move through the validation workflow, go directly to planning and scheduling, or in certain cases, go directly to the development steps.
  • workflowstaging-ref
    GitLab.org
    Merge request is deployed to the staging ref environment.
  • Merge request is deployed to the staging canary environment.
  • workflowstaging
    GitLab.org
    Merge request has been deployed to staging.gitlab.com.
  • Workflow label for validating that the proposed solution meets user needs. https://about.gitlab.com/handbook/product-development-flow/
  • workflowscheduling
    GitLab.org
    Issues that are ready for development but are not yet active (or have an associated release). https://about.gitlab.com/handbook/product-development-flow/
  • workflowrefinement
    GitLab.org
    Issues that need further input from team members in order for it to be "workflow::ready for development"
  • Merge 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.
  • (optional) PM and Design prioritized design backlog of the next issues to be done
  • workflowproduction
    GitLab.org
    Merge request has been deployed to GitLab.com
  • Workflow label for validating if the problem is customer relevant. https://about.gitlab.com/handbook/product-development-flow/#workflow-summary
  • Post-migrations on the merge request have been executed in staging.gitlab.com.
  • Post-migrations on the merge request have been executed in GitLab.com