Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.
  • critical
    GitLab.org / GitLab Development Kit
    Critical bugs that should be fixed as soon as possible.
  • typebug
    GitLab.org
    Issues that report undesirable or incorrect behavior. See https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification
  • Other labels

  • federal::CivCDM
    GitLab.org
    Continuous Diagnostics and Mitigation (US Civ gov Cybersecurity program) 100 OEMs, $1 Billion/year
  • IPS/IDS program for Internet access run by Verizon, ATT, CenturyLink, 2nd largest Cyber spend by Civ gov
  • Civilian, State, and Local gov Highly Adaptive Cybersecurity Services program for Threat Hunting (Pen testing, Risk assessments, high value assessments) services
  • Civilian gov mandated high value asset governance tied to CDM with Quarterly reports to Congress and Comptroller General
  • federal::DoDJRSS
    GitLab.org
    centralized IPS/IDS program for DoD/Allies coordinated by DISA, 37+ OEMs in the Joint Regional Security Stack. So big and awkwardly implemented it's drawn formal Pentagon criticism in 2017 and 2018. Multi-billion dollar IPS/IDS.
  • flakiness1
    GitLab.org
    Unhealthy test issues with 399 or more flakiness reports.
  • flakiness2
    GitLab.org
    Unhealthy test issues with between 37 and 398 flakiness reports.
  • flakiness3
    GitLab.org
    Unhealthy test issues with between 13 and 36 flakiness reports.
  • flakiness4
    GitLab.org
    Unhealthy test issues with less than 12 flakiness reports.
  • The test assumes the dataset is in a particular (usually limited) state, which might not be true depending on when the test run during the test suite.
  • The test is assuming a specific date or time.
  • The test use random values, that sometimes match the expectations, and sometimes not.
  • Test is failing due to a legitimate transient bug
  • The DOM selector used in the test is unreliable.
  • The test fails from time to time due to infrastructure issues.
  • follow-up
    GitLab.org
    Follow up issues that are created from merge requests
  • forking
    GitLab.org
    Issues related to creating, maintaining and deleting forks
  • found by e2e test
    GitLab.org
    Issue was discovered by the end-to-end test suite
  • Issue was discovered on canary.gitlab.com.