Labels can be applied to issues and merge requests. Group labels are available for any project within the group.
Labels
  • needs:steps to replicate
    An issue has been identified - but it needs more reliable guidance to reproduce the problem
  • needs:planning
    An issue has been identified - but it needs more planning/analysis before taking action
  • needs:documentation
    A draft solution has been prepared - but it needs documentation for users or developers
  • needs:concept approval
    Issue currently pending confirmation that a patch for it would be acceptable
  • git:cv
    Involves source code from the "cv" git repo
  • git:civicrm-wordpress
    Involves source code from the "civicrm-wordpress" git repo
  • git:civicrm-setup
    Involves source code from the "civicrm-setup" git repo
  • git:civicrm-packages
    Involves source code from the "civicrm-packages" git repo
  • git:civicrm-joomla
    Involves source code from the "civicrm-joomla" git repo
  • git:civicrm-drupal
    Involves source code from the "civicrm-drupal" git repo
  • git:civicrm-core
    Involves source code from the "civicrm-core" git repo
  • git:civicrm-backdrop
    Involves source code from the "civicrm-backdrop" git repo
  • epic:ro-db
    Tied to the overall goal of allowing read-only DB clones
  • epic
    This is a broad issue that is likely to entail multiple subordinate issues.
  • current sprint
  • comp:Search
    Built-in contact search components (Advanced Search, Search Builder, etc)
  • comp:Payments
    Payment processing
  • comp:OAuth
    Authentication API
  • comp:Import
    Built-in data-import system
  • comp:FormBuilder