Issues scheduled for the current milestone.

Issues that are a stretch goal for delivering in the current milestone. If these issues are not done in the current release, they will strongly be considered for the next release.

Getting idea to production running on Google Container Engine

Input from customer success team

For issues related to the stewardship of GitLab

Community contributions that have stalled, and need to be picked up by a merge request coach: https://about.gitlab.com/job-families/expert/merge-request-coach

Issues to put in the next patch release. Work on these first, and add the Pick Into Stable label to the merge request, along with the appropriate milestone.

Issues that were reported by Enterprise Edition subscribers. This label should be accompanied by either the 'bug' or 'feature proposal' label

Features and bugs reported by large enterprise customers. This label is in use by the product org, please post in #product Slack channel if you have questions.

Bugs that result in support having to access the production Rails console or filesystem to fix.

[deprecated] Please use "Seeking community contributions" instead. gitlab-org/developer-relations/contributor-success/team-task#77

Issues or MRs that introduce user-facing changes or impact the user experience. Applying this label to issues will signal a need for a designer.

Issues that require UX reseach

Visual improvement(s) to the existing user interface

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

https://about.gitlab.com/okrs/

Issues that report undesirable or incorrect behavior. See https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification

Please use the devops::plan label instead of this deprecated label. It is kept for historical issues.

Epics, issues, and merge requests related to product documentation.