Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.
  • (perceived) data loss
    GitLab.com / GitLab Infrastructure Team / Production Engineering
    An event that is seen as data loss from an external user
  • IncidentReview
    GitLab.com / GitLab Infrastructure Team
  • critical
    GitLab.com / GitLab Infrastructure Team / Production Engineering
    Things that really, really, really matter
  • priority1
    GitLab.com
    We will address this as soon as possible regardless of limit on our team capacity. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
  • severity1
    GitLab.com
    Blocker - applies to bugs and bug categories of availability, performance, security and ux. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity
  • severity2
    GitLab.com
    Critical - applies to bugs and bug categories of availability, performance, security and ux. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity
  • priority2
    GitLab.com
    priority 2 We will address this soon and will provide capacity from our team for it in the next few releases. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
  • priority3
    GitLab.com
    We want to address this but may have other higher priority items. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
  • priority4
    GitLab.com
    We don't have visibility when this will be addressed. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
  • unblocks others
    GitLab.com / GitLab Infrastructure Team / Production Engineering
    Help other people
  • goal
    GitLab.com / GitLab Infrastructure Team / Production Engineering
    Something we committed to do in the WoW
  • Other labels

  • Architecture review for cross functional collaboration.
  • Issues & Epics related to Account Based Marketing
  • label to track issues and epics the ABS team needs to interact with
  • Arkose
    GitLab.com
    Issues related to Arkose Labs part of the Anti-Abuse group of the Anti-abuse Stage
  • AssistTypeCloudInfra
    GitLab.com / GitLab Infrastructure Team
    Making or investigating infrastructure in AWS or GCP (S3/GCS, projects)
  • AssistTypeConfiguration
    GitLab.com / GitLab Infrastructure Team
    Configuration management (Chef/Ansible/Secrets) that requires infra access or help
  • AssistTypeDataRestore
    GitLab.com / GitLab Infrastructure Team
    Activity which required a restore from backup
  • AssistTypeDomain-DNS-SSL-Management
    GitLab.com / GitLab Infrastructure Team
    Assists with managing domains, ssl certs or DNS
  • AssistTypeGitLabAdmin
    GitLab.com / GitLab Infrastructure Team
    Things done by a GitLab Admin user - GitLab config
  • AssistTypeHandbookMaintenance
    GitLab.com / GitLab Infrastructure Team
    Redirects or other help for www-gitlab-com project and about.gitlab.com
  • AssistTypeSaaSQuestion
    GitLab.com / GitLab Infrastructure Team
    Questions about GitLab SaaS configuration or Shape of prod data
  • AssistingTeamData
    GitLab.com / GitLab Infrastructure Team
    Assists or asks from data team
  • AssistingTeamDevelopment
    GitLab.com / GitLab Infrastructure Team
    Assists or asks from engineering team
  • AssistingTeamGrowth&Fullfillment
    GitLab.com / GitLab Infrastructure Team
    Helping with customers, license, version
  • AssistingTeamIT
    GitLab.com / GitLab Infrastructure Team
    Assists or asks from it/ops team
  • AssistingTeamInfrastructure
    GitLab.com / GitLab Infrastructure Team
    Assists to infra team itself - usually corrective actions