Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.

Other labels

  • quick win
    GitLab.com
    Used to identify issues that are quick wins
  • rapid action
    GitLab.com
    Label used for tagging items related to a rapid action response (https://about.gitlab.com/handbook/engineering/development/#rapid-action-issue)
  • regression
    GitLab.com
    Regressions that break working behavior
  • release
    GitLab.com
    Issues and merge requests related to GitLab stable releases
  • release post item
    GitLab.com
    Features that will be included in the monthly release blog post
  • release-blocker
    GitLab.com
    An issue or a task blocking a release, either auto_deploy or customer packages
  • Issues related to creating a single release-tools pipeline that coordinates other release pipelines gitlab-com/gl-infra&154
  • riskescalation
    GitLab.com
    Label used to escalate risks identified on issues or MRs. When the label is applied, a risk assessment is created on our GRC system, ZenGRC.
  • sales dev ops BDR DRIs Assigned
    GitLab.com / marketing
    This label is meant to be used for FM BDR request issues, after the DRIs from the BDR-side have been assigned to the issue.
  • sales dev ops BDR Pre-Work Complete
    GitLab.com / marketing
    This label is meant to be used for FM requests after the BDR DRIs have completed all required pre-event tasks and outreach
  • sales dev ops Escalated Issues
    GitLab.com / marketing
    This label denotes issues we're actively working on that have been escalated to other teams that we are waiting to hear back from you.