Labels

applies to work related to the product development flow

A discovery issue intended for UX, PM, FE, and BE to discuss the problem and potential solutions. The final output for this issue could be a doc of requirements, a design artifact, or even a prototype. The solution will be developed in a subsequent milestone.

applies to work related to the product handbook

Assigned to MRs when danger bot detects changes to tracking/metrics related files to kick off approval process.

Product Analytics(Telemetry) changes are reviewed and ready to be approved by Product Analytics(Telemetry) Reviewer/Maintainer

Product Analytics(Telemetry) changes require a review from Product Analytics(Telemetry) Reviewer/Maintainer

This epic or issue needs product review to validate need and/or schedule.

In order to keep a manageable backlog of work we are actively focusing on, we apply the ~"product planning::parked" label to the epics/issues that we intend to check regularly, but do not plan any work on them currently.

This label signifies work that we are preparing as a candidate for an upcoming Quarterly plan. While in `scoping` we are ensuring the goal of the work, the usability expectations, what's included and not included are clear so that engineering can provide an estimate/feasibility of the work in the upcoming quarter.

Issues for the Product team. Covers issues that still need to be worked out before UX / Dev can work on it

Changes to the GitLab application requested by the GitLab Infrastructure Team that would improve the administration and management of GitLab.com

Issues that block the deployment to production

Used to identify all issues and epics related to the Cloud Sync Program

Issues generally related to projects.

Issues related to creating projects.

Issues related to importing repositories from GitLab or external systems

Instance-level, Group-level or Built-in Project Templates