Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
accel abmFYIGitLab.com / marketingFor all issues that the Acceleration ABM SDR team should be aware of
-
accel abmcompletedGitLab.com / marketingFor issues that have been completed or resolved by the Acceleration ABM team
-
accel abmin progressGitLab.com / marketingIssues that the Acceleration ABM team is currently working on
-
accel abmqueueGitLab.com / marketingIssues or requests related to the accel abm sdr team that are currently pending
-
availabilitylimitGitLab.comGitLab, like most large applications, enforces limits within certain features. The absences of limits can impact security, performance, and availability. For this reason issues related to limits are considered as another category of ~"type::bug". https://about.gitlab.com/handbook/engineering/quality/issue-triage/#limit-related-bugs
-
base customer advocacy programGitLab.com / marketingRequest of customers in the Base program for any advocacy asks. https://docs.google.com/document/d/1zS9Xodyqu5-2Ng7ko0X9qS3YeIcyAW-dArj5asKJ2zE/edit
-
blocks deploymentsGitLab.comAny item that should prevent deployments to gstg (staging) and gprd (production) should have this label applied.
-
blocks feature-flagsGitLab.comAny item that should prevent feature-flag changes from proceeding should have this label applied.
-
breaking changeGitLab.comA backwards-incompatible change that will need to be made with the next major release. See https://docs.gitlab.com/ee/development/contributing/index.html#breaking-changes
Prioritized