Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.
  • DBRE Headroom
    GitLab.org / GitLab
  • groupcustom models
    GitLab.org
  • grouppersonal productivity
    GitLab.org
    Group covering Navigations, Settings, and Notifications.
  • groupglobal search
    GitLab.org
    Issues belonging to the Global Search group of the Core Platform stage of the DevOps lifecycle.
  • groupprovision
    GitLab.org
    Issues belonging to the Provision group of the Fulfillment stage of the DevOps lifecycle. See https://about.gitlab.com/handbook/product/categories/#provision-group
  • Category:Global Search
    GitLab.org
    Issues related to search using the search field in the top navigation bar
  • grouppurchase [DEPRECATED]
    GitLab.org
    [DEPRECATED] Adoption was a group in the Fulfillment section. See https://about.gitlab.com/handbook/product/categories/#fulfillment-section
  • Model Experiments
    GitLab.org
    Model Experiments allows Data Scientists to track candidates for their machine learning models
  • groupsubscription management
    GitLab.org
    Issues and epics belonging to the Subscription Management group of the Fulfillment stage.
  • 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
  • grouputilization
    GitLab.org
    label for the fulfillment subscription team
  • 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
  • Category:Code Search
    GitLab.org
    Code Search Category is part of Global Search that focuses on searching through Code Across Repositories
  • Architecture Evolution Blueprint
    GitLab.org
    Changes to Architecture Evolution Blueprints described at https://about.gitlab.com/handbook/engineering/architecture/workflow/
  • groupanalyzer frontend
    GitLab.org
    Secure: Issues being worked on by the Secure Analyzer Frontend Team
  • grouppubsec services
    GitLab.org
    SaaS services for the US Public Sector
  • quad-planningcomplete-no-action
    GitLab.org
    Issue has gone through Quad Planning process (PM,Dev,UX,QE) and does not require any additional action
  • Category:US Public Sector Services
    GitLab.org
    SaaS services for the US Public Sector
  • StORMIntake
    GitLab.org
    Label to communicate potential security operational risks to the Security Risk Team
  • StORMNeeds Additional Information
    GitLab.org
    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.
  • StORMUnder Assessment
    GitLab.org
    Label used to note the Security Risk Team is currently assessing a potential risk
  • milestonep1
    GitLab.org
    Priority 1 for the assigned milestone.
  • Risk and Field Security
    GitLab.org
    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://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/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://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority
  • priority3
    GitLab.org
    We want to address this but may have other higher priority items. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority
  • priority4
    GitLab.org
    We don't have visibility when this will be addressed. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/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

  • CI PK conversion
    GitLab.org
    Issues related to converting primary keys to BigInt in the CI database
  • CI PK conversion
    GitLab.org / GitLab
    Issues related to converting primary keys to BigInt in the CI database
  • CI Pipeline Editor
    GitLab.org / GitLab
    Issues related to the Pipeline Editor and the pipeline authoring group PM @dhershkovitch
  • CI artifacts
    GitLab.org
    Issues related to GitLab CI build artifacts: http://doc.gitlab.com/ce/ci/build_artifacts/README.html
  • CI data partitioning
    GitLab.org
    Data Partitioning effort in support of implementing the CI/CD Time Decay blueprint - https://docs.gitlab.com/ee/architecture/blueprints/ci_data_decay/
  • CI integrations
    GitLab.org
    Issues related to the using CI with specific other platforms (for example, Docker, Java, or Mobile)
  • CI job token
    GitLab.org
    Issues related to CI_JOB_TOKEN
  • CI jobs [DEPRECATED]
    GitLab.org
    Issues related to CI jobs including the jobs page
  • CI lint
    GitLab.org / GitLab
    This label is related for GitLab CI linting capabilities
  • CI permissions
    GitLab.org
    Issues related to CI_JOB_TOKEN and CI authentication.
  • CI reports
    GitLab.org / GitLab
    Feature in Category:CI
  • CI variables
    GitLab.org
    Relates to functionality surrounding pre-defined and user-defined variables available in the Build environment.
  • CI/CD Core Platform
    GitLab.org
    Issues and merge requests related to the core of GitLab CI/CD platform - pipeline configuration, pipeline creation, pipeline processing, pipeline statues, artifacts.
  • CI/CD Settings [DEPRECATED]
    GitLab.org
    Feature in Category:CI
  • CI/CD UX Team
    GitLab.org
    Used by the UX CI/CD Team to track process and activities (DRI: Product Design Manager) https://about.gitlab.com/handbook/engineering/ux/stage-group-ux-strategy/ci-cd/
  • CISA Known Exploited Vulnerability
    GitLab.org
    Vulnerabilities in CISA's KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
  • CISP1
    GitLab.org
    Priority Score based on Customer Issues Prioritization Framework (https://about.gitlab.com/handbook/product/product-processes/customer-issues-prioritization-framework/#priority-score); From highest to lowest priority: CISP::1, CISP::2, CISP::3, CISP::4. These priorities represent separate buckets for features and bugs. And these are again separated by group. Currently, this label is only applied to ~type::bug and ~"group:source code"
  • CISP2
    GitLab.org
    Priority Score based on Customer Issues Prioritization Framework (https://about.gitlab.com/handbook/product/product-processes/customer-issues-prioritization-framework/#priority-score); From highest to lowest priority: CISP::1, CISP::2, CISP::3, CISP::4. These priorities represent separate buckets for features and bugs. And these are again separated by group. Currently, this label is only applied to ~type::bug and ~"group:source code"
  • CISP3
    GitLab.org
    Priority Score based on Customer Issues Prioritization Framework (https://about.gitlab.com/handbook/product/product-processes/customer-issues-prioritization-framework/#priority-score); From highest to lowest priority: CISP::1, CISP::2, CISP::3, CISP::4. These priorities represent separate buckets for features and bugs. And these are again separated by group. Currently, this label is only applied to ~type::bug and ~"group:source code"
  • CISP4
    GitLab.org
    Priority Score based on Customer Issues Prioritization Framework (https://about.gitlab.com/handbook/product/product-processes/customer-issues-prioritization-framework/#priority-score); From highest to lowest priority: CISP::1, CISP::2, CISP::3, CISP::4. These priorities represent separate buckets for features and bugs. And these are again separated by group. Currently, this label is only applied to ~type::bug and ~"group:source code"