Generates a 'top' release post item for this issue in the www-gitlab-com project

An issue or a task blocking a release, either auto_deploy or customer packages

Issues in triage to be worked on by Release UX team

As a merge request is included in self-managed releases, it will receive the released::candidate label when the release candidate it is included in is deployed to pre.gitlab.com. https://about.gitlab.com/handbook/engineering/releases/#self-managed-releases-2

A merge request will receive the released::published label when included in a packaged release, such as 13.6.0 or 13.5.2, and deployed to release.gitlab.net for both automated and manual testing. https://about.gitlab.com/handbook/engineering/releases/#self-managed-releases-2

Changes requested by customers seeking to replace Gerrit (see also #replacing-gerrit on GitLab internal Slack)

Issues related to the Reply by email feature: https://docs.gitlab.com/ee/administration/reply_by_email.html

Issues related to reporting

Issues related to Git, from commits, branches, and tags to files, diffs, and the blame view

Issues that have been reproduced on GitLab.com

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

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.

features related to resource groups

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.

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.

Items related to increasing customer retention that fall outside of Group::Retention. Used for tracking.

Issues identified in the 11.10 retrospective

Identified improvements we could make as a result of the 11.4 retrospective.

Issues identified in the 11.5 retrospective