Other labels
contributorgrowthinternal
GitLab.org
Active issues for this quarter that address internal technical debt or improve workflow processes in support of the open source growth strategy: https://about.gitlab.com/handbook/engineering/open-source/growth-strategy.html
contributorgrowthinternal [inactive]
GitLab.org
Inactive issues that are not for the current quarter that address internal technical debt or improve workflow processes in support of the open source growth strategy: https://about.gitlab.com/handbook/engineering/open-source/growth-strategy.html
contributorgrowthjourney
GitLab.org
Active issues for this quarter to improve contributor journey as part of the open source growth strategy: https://about.gitlab.com/handbook/engineering/open-source/growth-strategy.html
contributorgrowthjourney [inactive]
GitLab.org
Inactive issues that are not for the current quarter to improve contributor journey as part of the open source growth strategy: https://about.gitlab.com/handbook/engineering/open-source/growth-strategy.html
contributorgrowthscale the community
GitLab.org
Active issues for this quarter to scale the community as part of the open source growth strategy: https://about.gitlab.com/handbook/engineering/open-source/growth-strategy.html
Inactive issues that are not for the current quarter to scale the community as part of the open source growth strategy: https://about.gitlab.com/handbook/engineering/open-source/growth-strategy.html
creator-pairing
GitLab.org
Issues created during creator-pairing program. See #creator-pairing slack channel or ping @dzaporozhets
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.
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.
Prioritized