Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.
  • Changelog
    GitLab.org / release-tools
    Issues and merge requests related to the Changelog Compilation functionality
  • ChatOps
    GitLab.org / release-tools
    Issues and merge requests related to ChatOps functionality
  • Upstream Merge
    GitLab.org / release-tools
    Issues and merge requests related to the Automatic Upstream Merge functionality

    • Other labels

  • cpuamd64
    GitLab.org
    Issues related to x86_64/amd64 CPU
  • cpuarm64
    GitLab.org
    Issues related to ARMv8 AArch64 / arm64 CPU
  • cpuppc64le
    GitLab.org
    Issues related to IBM Power / ppc64le CPU
  • cpuriscv64
    GitLab.org
    Issues related to the RISC-V 64-bit CPU
  • cpus390x
    GitLab.org
    Issues related to IBM Z / s390x CPU
  • creator-pairing
    GitLab.org
    Issues created during creator-pairing program. See #creator-pairing slack channel or ping @dzaporozhets
  • critical security release
    GitLab.org
    A tracking issue for a critical security release
  • critical-customer-escalation
    GitLab.org
    Customer bugs that are escalated involving CS / TAM / Quality leadership
  • cross-group
    GitLab.org
    Denotes the issue belongs to another Group (or even Stage) but is being worked by a different Group's engineering team.
  • custom fields
    GitLab.org
  • 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 priority1
    GitLab.org
    Used to denote the relative customer priority when including a link to SFDC or ZenDesk on an issue or epic. 1 is the lowest and 10 is the highest. See https://about.gitlab.com/handbook/product/how-to-engage/#feedback-template for more info.
  • customer priority10
    GitLab.org
    Used to denote the relative customer priority when including a link to SFDC or ZenDesk on an issue or epic. 1 is the lowest and 10 is the highest. See https://about.gitlab.com/handbook/product/how-to-engage/#feedback-template for more info.
  • customer priority2
    GitLab.org
    Used to denote the relative customer priority when including a link to SFDC or ZenDesk on an issue or epic. 1 is the lowest and 10 is the highest. See https://about.gitlab.com/handbook/product/how-to-engage/#feedback-template for more info.
  • customer priority3
    GitLab.org
    Used to denote the relative customer priority when including a link to SFDC or ZenDesk on an issue or epic. 1 is the lowest and 10 is the highest. See https://about.gitlab.com/handbook/product/how-to-engage/#feedback-template for more info.
  • customer priority4
    GitLab.org
    Used to denote the relative customer priority when including a link to SFDC or ZenDesk on an issue or epic. 1 is the lowest and 10 is the highest. See https://about.gitlab.com/handbook/product/how-to-engage/#feedback-template for more info.
  • customer priority5
    GitLab.org
    Used to denote the relative customer priority when including a link to SFDC or ZenDesk on an issue or epic. 1 is the lowest and 10 is the highest. See https://about.gitlab.com/handbook/product/how-to-engage/#feedback-template for more info.
  • customer priority6
    GitLab.org
    Used to denote the relative customer priority when including a link to SFDC or ZenDesk on an issue or epic. 1 is the lowest and 10 is the highest. See https://about.gitlab.com/handbook/product/how-to-engage/#feedback-template for more info.
  • customer priority7
    GitLab.org
    Used to denote the relative customer priority when including a link to SFDC or ZenDesk on an issue or epic. 1 is the lowest and 10 is the highest. See https://about.gitlab.com/handbook/product/how-to-engage/#feedback-template for more info.
  • customer priority8
    GitLab.org
    Used to denote the relative customer priority when including a link to SFDC or ZenDesk on an issue or epic. 1 is the lowest and 10 is the highest. See https://about.gitlab.com/handbook/product/how-to-engage/#feedback-template for more info.