Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
  • 1st contribution
    First contribution from a community member
  • 2FA
  • Accepting merge requests
    Issues opened for contribution from the Community. Issue's weight is an estimation of complexity. Please mention @markglenfletcher if you have any questions :)
  • Architecture decision
    Important architecture decision
    Please use the Verify or Release team label instead of this no longer used label. It is kept for historical issues.
  • CS Top 10 List for Product (2018Q3)
  • CSS Component
    Adding or changing a CSS component
  • Charts
    Related to the Charts components built on gitlab-ui
  • Cloud Native
  • Cloud Spend
    Issues related to cloud provider usage fees, and particularly reducing cloud spend
  • Community contribution
    Issues that have been scheduled for an upcoming release and are actively being worked on by our community
  • Configure
    Issues for the configure team. Covers Auto DevOps, Kubernetes integration, ChatOps, Chat integration, etc.
  • Create
    Issues for the Create team. Covers Repositories, Merge Requests, Web IDE, Wiki and Snippets.
  • Current
    Epics that are being currently worked on.
  • Deliverable
    Issues scheduled for the current milestone. GitLab ambitiously over-schedules and may only deliver about 70% of scheduled issues.
  • Delivery
  • Dependency Proxy
    Features that apply to proxification/caching of packages
  • Dev Advocacy
    Feature proposals or bug reports, collected by developer advocates
  • Distributed Tracing
  • Distribution
    Issues for the Distribution team. Covers everything related to the GitLab omnibus package and Helm charts:,