Skip to content

Prioritized labels 7

Drag to reorder prioritized labels and change their relative priority.
  • security
    GitLab.org
    Issues related to the security of GitLab or its dependencies. Please report vulnerabilities responsibly per https://about.gitlab.com/security/disclosure/
  • customer
    GitLab.org
    Issues that were reported by Enterprise Edition subscribers. This label should be accompanied by either the 'bug' or 'feature proposal' label
  • customer+
    GitLab.org
    Features 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.
  • regression
    GitLab.org
    Issues with this label are regressions from the previous non-patch release
  • typebug
    GitLab.org
    Issues that report undesirable or incorrect behavior. See https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification
  • direction
    GitLab.org
    Issues for important features that are on our roadmap: https://about.gitlab.com/direction/
  • high priority
    GitLab.org / gitlab-runner
    Other important issues

    • Labels 3,052

  • product handbook
    GitLab.org
    applies to work related to the product handbook
  • product intelligence
    GitLab.org
    Assigned to MRs when danger bot detects changes to tracking/metrics related files to kick off approval process.
  • product intelligenceapproved
    GitLab.org
    Product Analytics(Telemetry) changes are reviewed and ready to be approved by Product Analytics(Telemetry) Reviewer/Maintainer
  • product intelligencereview pending
    GitLab.org
    Product Analytics(Telemetry) changes require a review from Product Analytics(Telemetry) Reviewer/Maintainer
  • product metrics
    GitLab.org
  • product planningneeds review
    GitLab.org
    This epic or issue needs product review to validate need and/or schedule.
  • product planningparked
    GitLab.org
    In order to keep a manageable backlog of work we are actively focusing on, we apply the ~"product planning::parked" label to the epics/issues that we intend to check regularly, but do not plan any work on them currently.
  • product planningscoping
    GitLab.org
    This label signifies work that we are preparing as a candidate for an upcoming Quarterly plan. While in `scoping` we are ensuring the goal of the work, the usability expectations, what's included and not included are clear so that engineering can provide an estimate/feasibility of the work in the upcoming quarter.
  • product work
    GitLab.org
    Issues for the Product team. Covers issues that still need to be worked out before UX / Dev can work on it
  • production request
    GitLab.org
    Changes to the GitLab application requested by the GitLab Infrastructure Team that would improve the administration and management of GitLab.com
  • productionblocker
    GitLab.org
    Issues that block the deployment to production
  • prog-cloud-sync
    GitLab.org
    Used to identify all issues and epics related to the Cloud Sync Program
  • project
    GitLab.org
    Issues generally related to projects.
  • project creation
    GitLab.org
    Issues related to creating projects.
  • project-templates
    GitLab.org
    Instance-level, Group-level or Built-in Project Templates
  • prototypebeta
    GitLab.org
    Used to label features that are in Beta https://docs.gitlab.com/ee/policy/alpha-beta-support.html#beta
  • prototypeexperiment
    GitLab.org
    Used to label features that are Experimental (https://docs.gitlab.com/ee/policy/alpha-beta-support.html#experiment)
  • prototypegeneral_availability
    GitLab.org
    Used to label features that are moving to General Availability https://docs.gitlab.com/ee/policy/alpha-beta-support.html#generally-available-ga
  • pservice-fix
    GitLab.org
    This tag tracks professional services fixes across GitLab
  • published
    GitLab.org
    This merge request will be published in a self-managed GitLab release. This label is added using the Release Tools project, and should not be manually added to merge requests.