Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.

Other labels

  • prodops:direction
    GitLab.org
    Applies to epics, issues or MRs that should be highlighted on a Product Operations direction page.
  • Applies to to Product Operations work focusing on building qualitative & quantitative feedback loops.
  • prodops:knowledge
    GitLab.org
    Applies to to Product Operations work focusing on scaling product knowledge.
  • prodops:outcomes
    GitLab.org
    Applies to to Product Operations work supporting operationalizing outcome driven products.
  • prodops:related
    GitLab.org
    This label represents is used when an epic, issue or MR does not required direct contribution from Product Operations but required their awareness as it affects workflows, documentation, or is otherwise a dependency for Product Operations work.
  • prodops:release
    GitLab.org
    Applies to epics, issues or MRs that should be highlighted on a Product Operations release page.
  • 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.
  • product handbook
    GitLab.org
    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.
  • product work
    GitLab.org
    Issues for the Product team. Covers issues that still need to be worked out before UX / Dev can work on it
  • production request
    GitLab.org
    Changes to the GitLab application requested by the GitLab Infrastructure Team that would improve the administration and management of GitLab.com
  • productionblocker
    GitLab.org
    Issues that block the deployment to production
  • prog-cloud-sync
    GitLab.org
    Used to identify all issues and epics related to the Cloud Sync Program