Issues and Merge Requests related to upgrading to Rails 5.2

Issues related to analytics, like feature usage, graphs and data we can display in GitLab UI

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

End-to-end user flow encompassing multiple GitLab features

The content of the issue or comments contains to references to private user information, such as private repository paths and its contents should remain confidential indefinitely. This is usually primarily used for ~security or production issues.

Merge requests which have been reviewed and can be merged by a maintainer with sufficient knowledge in the given area. For merging the merge request just assign to yourself and remove this label.

Issues for the Meltano team.

Issues related to the observability of the GitLab application

This bug has had the default priority applied. Feel free to override. More info: gitlab-org/quality/triage-ops#29

This bug has had the default severity applied. Feel free to override. More info: gitlab-org/quality/triage-ops#29

&332

Epics that are being currently worked on.

Issues that have been scheduled for an upcoming release and are actively being worked on by our community

New changes that can be disabled using a feature flag, or existing feature flags that are being removed.

Issues concerning the installation, upgrade or administration of the Geo feature

Issues related to cloud provider usage fees, and particularly reducing cloud spend

Map business value, people, processes, and data across value streams.

Mitigate risks in large enterprises, including (but not limited to) enforced workflows, approvals, templating of various artifacts like issues and code files, compliance, traceability of requirements, and auditing/logging.

Issues for Ruby teams that require some knowledge of Go, because they may require changes in Gitaly, Workhorse, etc