Skip to content

Prioritized labels 5

Drag to reorder prioritized labels and change their relative priority.
  • integration failure
    GitLab.org / GitLab QA
    Integration failures that have been found by GitLab QA
  • typebug
    GitLab.org
    Issues that report undesirable or incorrect behavior. See https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification
  • maintenancerefactor
    GitLab.org
    Issues related to things that need improvement and that have been left behind due to high velocity of development
  • new scenario
    GitLab.org / GitLab QA
    Describes a new scenario to add to the QA suite.
  • Labels 2,847

  • Indicates the work was associated to HackerOne administration
  • Indicates the work was associated to the AppSec HackerOne duties
  • AppSecWorkTypeKR
    GitLab.org
    Work associated with AppSec OKRs and KRs
  • AppSec work not covered by other AppSecWorkType labels
  • Indicates the work was associated to a SIRT incidents and/or Security communications work
  • Indicates the work was associated to the AppSec Security release task issue duties
  • AppSec Threat Modeling work
  • Indicates the work was associated to our tools and automation
  • This label is used by the Application Security team to apply when the IC on rotation gets pinged during their triage rotation
  • Indicates the work was associated to the AppSec Federal AppSec VAT duties
  • AppSec work associated with stable counterpart duties
  • Indicates the work is done, or the rotation has finished.
  • Indicates the issue is actively being worked on, or the rotation is in progress.
  • Indicates that work has been triaged, scoped, and is ready to be worked on in the assigned milestone.