Prioritized Labels

Star labels to start sorting by priority

Other Labels
  • Accepting merge requests
    Issues opened for contribution from the Community. Issue's weight is an estimation of complexity. Please mention @gitlab-org/coaches if you have any questions :)
    • Project label
  • Community contribution
    Issues that have been scheduled for an upcoming release and are actively being worked on by our community
    • Project label
  • Configure
    Issues for the configure team. Covers Auto DevOps, Kubernetes integration, ChatOps, Chat integration, etc.
    • Project label
  • Create
    Issues for the Create team. Covers Repositories, Merge Requests, Web IDE, Wiki and Snippets.
    • Project label
  • Deliverable
    Issues scheduled for the current milestone.
    • Project label
  • Design documentation
    Issues involving creating or updating documentation on design.GitLab.com. The UX team leads this effort.
    • Project label
  • Documentation
    Issues for the Documentation team. Covers our efforts to continuously improve and maintain the quality of GitLab documentation
    • Project label
  • Doing
    • Project label
  • Manage
    Issues for the Manage team. Covers Administration, Analytics, Groups, Projects and GitLab.com
    • Project label
  • Monitor
    Issues for the Monitor team. Covers everything related to prometheus monitoring, including GitLab instances and user-applications
    • Project label
  • OKR
    • Project label
  • P1
    Priority 1 - Urgent (SLA for bugs and security issues: Fix ASAP in the current release and within 30 days) See contributing/issue_workflow.md for details.
    • Project label
  • P2
    Priority 2 - High (SLA for bugs and security issues: Fix in the next release or within 60 days) See contributing/issue_workflow.md for details.
    • Project label
  • Package
    Work for the Package department. See https://about.gitlab.com/handbook/product/categories/. Ping @jlenny or @dimitrieh for questions and comments.
    • Project label
  • Plan
    • Project label
  • Platform [DEPRECATED]
    Please use the Create or Plan team label instead of this no longer used label. It is kept for historical issues.
    • Project label
  • Release
    Issues for the Release team. Covers Continuous Delivery, Pages, Review Apps, and Incremental Rollout.
    • Project label
  • S2
    Severity 2 - Critical: Broken Feature, workaround too complex & unacceptable. See CONTRIBUTING.md for examples
    • Project label
  • Secure
    Issues for the Secure team. Covers security of end-user applications, like SAST, Dependency Scanning, etc.
    • Project label
  • Stretch
    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.
    • Project label