Labels
Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels 3,560
-
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 Git, from commits, branches, and tags to files, diffs, and the blame view
-
Issues that have been reproduced on GitLab Dedicated
-
Issues that have been reproduced on GitLab Dedicated for Gov
-
Issues that have been reproduced on GitLab Self-Managed
-
Issues / tasks that require cross functional reviews.
-
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.
-
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.
-
Identified improvements we could make as a result of the 11.4 retrospective.