Issues related to GitLab's (ab)use of its database

Issues for the Plan stage of the DevOps lifecycle (e.g. Project Management, Agile Portfolio Management, Requirements Management)

Issues for the Create stage of the DevOps lifecycle (e.g. Source Code Management, Design Management, Web IDE, Code Review, Gitter)

Issues for the Verify stage of the DevOps lifecycle (e.g. CI, Code Quality, Usability Testing)

Issues for the Package stage of the DevOps lifecycle (e.g. Container Registry, Dependency Proxy)

[DEPRECATED] should use devops::deploy. Issues for the Release stage of the DevOps lifecycle (e.g. CD, Release Automation, Pages, Review apps)

[DEPRECATED] should use devops::deploy now. Issues for the Configure stage of the DevOps lifecycle (e.g. Auto DevOps , Kubernetes Configuration, ChatOps, Serverless, PaaS)

Issues for the Monitor stage of the DevOps lifecycle (e.g. Metrics , Tracing, Logging, Error Tracking, Cluster Monitoring)

Issues for Infrastructure Configuration, part of the Configure stage of the DevOps lifecycle

Issues for Operations, part of the Configure stage of the DevOps lifecycle

Issues for Feature Management, part of the Release stage of the DevOps lifecycle

Issues for Application Performance Monitoring (APM), part of the Monitor stage of the DevOps lifecycle

Issues related to updating to newer versions of the dependencies GitLab requires (Ruby gems, NPM packages, GitLab Workhorse, GitLab Shell, Gitaly...)

Features or changes limited or intended as part of GitLab Ultimate.

Issues that have been reproduced on GitLab.com

Issues related to markdown/image emojis, `gl_emoji`

Issues and MRs related to the subgroups feature

Issues related to the To-Do List feature: https://docs.gitlab.com/ee/user/todos.html

Feature vision in Plan stage: &781