Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.

Other labels

  • resource groups
    GitLab.org
    features related to resource groups
  • resource planning
    GitLab.org
    Manage your capacity and resources across a portfolio of products and programs. Track estimated effort vs actuals, see over and under capacity commitments, and visualize these on your roadmap, high level burn-down charts, and reports.
  • responsive
    GitLab.org
    Pertaining to responsive web design which is aimed at crafting sites to provide an optimal viewing and interaction experience—easy reading and navigation with a minimum of resizing, panning, and scrolling—across a wide range of devices.
  • retention
    GitLab.org
    Items related to increasing customer retention that fall outside of Group::Retention. Used for tracking.
  • retrospective:11.10
    GitLab.org
    Issues identified in the 11.10 retrospective
  • retrospective:11.4
    GitLab.org
    Identified improvements we could make as a result of the 11.4 retrospective.
  • retrospective:11.5
    GitLab.org
    Issues identified in the 11.5 retrospective
  • retrospective:11.6
    GitLab.org
    Issues identified in the 11.6 retrospective
  • retrospective:11.7
    GitLab.org
    Issues identified in the 11.7 retrospective
  • retrospective:11.8
    GitLab.org
    Issues identified in the 11.8 retrospective
  • retrospective:11.9
    GitLab.org
    Issues identified in the 11.9 retrospective
  • reverted
    GitLab.org
    This MR contains changes that were reverted (automatically), and have to be re-added by the author.
  • reviewers
    GitLab.org
    Related to the merge request reviewers feature
  • rich blob viewer
    GitLab.org
    Relating to the rich blob viewer features
  • risk management
    GitLab.org
    All issues related to risk management
  • The vulnerability is accepted (often due to very low risk) and it will not be fixed.
  • The vulnerability was incorrectly reported and is not actually present or exploitable in any way.
  • The severity level downgraded because compensating controls in place AND the risk is accepted (i.e. will not be fixed).
  • The severity level should be downgraded due to compensating controls in place.
  • The issue is not able to be remediated due to technical constraints. This state will keep the issue open until it is able to be remediated in the future.