Skip to content

Prioritized labels 25

Drag to reorder prioritized labels and change their relative priority.
  • Category:Serverless
    GitLab.org
    All issues and MRs related to the Serverless category within devops::configure. https://about.gitlab.com/direction/configure/serverless/
  • dockerfile
    GitLab.org / GitLab Docs
    Related to the dockerfiles present in the gitlab-docs project
  • Category:Chaos Engineering
    GitLab.org
    Issues related to chaos engineering (part of ~devops:configure stage)
  • docs-discussion
    GitLab.org / GitLab Docs
    Ongoing discussions for the docs team
  • devopsconfigure [DEPRECATED]
    GitLab.org
    [DEPRECATED] should use devops::deploy now. Issues for the Configure stage of the DevOps lifecycle (e.g. Auto DevOps , Kubernetes Configuration, ChatOps, Serverless, PaaS)
  • kramdown
    GitLab.org / GitLab Docs
    Kramdown related issues
  • Category:Infrastructure as Code
    GitLab.org
    All issues and MRs related to the Infrastructure as Code category within devops::configure. https://about.gitlab.com/direction/configure
  • [deprecated] Accepting merge requests
    GitLab.org
    [deprecated] Please use "Seeking community contributions" instead. gitlab-org/developer-relations/contributor-success/team-task#77
  • Category:Cluster Monitoring
    GitLab.org
    Issues belonging to the Monitor stage Health group for product category Cluster Monitoring
  • Category:Auto DevOps
    GitLab.org
    Issues for Auto DevOps, part of the Configure stage of the DevOps lifecycle
  • Category:Code Quality
    GitLab.org
    All issues and MRs related to the Code Quality category. See https://about.gitlab.com/direction/secure/static-analysis/code-quality/
  • Category:Container Registry
    GitLab.org
    Category label - Features that apply to management container registries
  • groupconfigure [DEPRECATED]
    GitLab.org
    [DEPRECATED] should use group::environments. Issues belonging to the Configure group of the Configure stage of the DevOps lifecycle. See https://about.gitlab.com/handbook/product/categories/#configure-group
  • Category:Continuous Integration
    GitLab.org
    All issues and MRs related to the continuous integration category within devops:verify https://about.gitlab.com/direction/verify/continuous_integration
  • [Deprecated] Category:Runner
    GitLab.org
    Please select Runner Core, Runner SaaS, or Runner Fleet
  • infrastructure configuration
    GitLab.org
    Issues for Infrastructure Configuration, part of the Configure stage of the DevOps lifecycle
  • operations
    GitLab.org
    Issues for Operations, part of the Configure stage of the DevOps lifecycle
  • Category:Cluster Cost Optimization
    GitLab.org
    Issues related to the "cluster cost optimization" category of the configure stage. See &503
  • Charts
    GitLab.org
    Related to the Charts components built on gitlab-ui
  • Category:Cloud Native Installation
    GitLab.org
    Related to https://gitlab.com/gitlab-org/charts/gitlab
  • development guidelines
    GitLab.org
    Changes or updates to the development guidelines in the /development directory in the GitLab documentation. (Info: https://docs.gitlab.com/ee/development/)
  • groupsource code
    GitLab.org
    Issues belonging to the Source Code group of the Create stage of the DevOps lifecycle. See https://about.gitlab.com/handbook/product/categories/#source-code-group
  • grouprunner
    GitLab.org
    Issues belonging to the Runner group of the Verify stage of the DevOps lifecycle.
  • Category:Kubernetes Management
    GitLab.org
    Relating the `Kubernetes Management` category within the configure stage
  • rails6
    GitLab.org
    Issues and Merge Requests related to upgrading to Rails 6

    • Labels 3,012

  • requires production access
    GitLab.org
    Bugs that result in support having to access the production Rails console or filesystem to fix.
  • researched [DEPRECATED]
    GitLab.org
    User feedback (from the wider GitLab community) gathered via multiple comments, a survey, UsabilityHub study, card sort/tree test, usability testing and/or user interviews.
  • 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
  • revert // rollback
    GitLab.org / GitLab Docs
  • 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
  • risk treatmentaccept
    GitLab.org
    The vulnerability is accepted (often due to very low risk) and it will not be fixed.
  • risk treatmentfalse positive
    GitLab.org
    The vulnerability was incorrectly reported and is not actually present or exploitable in any way.