Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.

Other labels

  • 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
  • A tracking issue for a critical security release
  • 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.
  • 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.
  • customer priority9
    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 success
    GitLab.org
    Input from customer success team
  • 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.
  • Part of the Customer Happy Paths Project