Labels can be applied to issues and merge requests. Group labels are available for any project within the group.
Labels
  • sig:lexim
    Indicates an issue whose fix is helpful on our path to renewal via form builder/apiv4 & other leaps
  • sig:legacy-ui
    Indicates bug relates to a part of the UI we anticipate being replaced by the form builder approach
  • needs:documentation
    A draft solution has been prepared - but it needs documentation for users or developers
  • comp:Search
    Built-in contact search components (Advanced Search, Search Builder, etc)
  • sig:performance
    (Significance) Affects how *quickly* the system runs
  • epic:ro-db
    Tied to the overall goal of allowing read-only DB clones
  • needs:steps to replicate
    An issue has been identified - but it needs more reliable guidance to reproduce the problem
  • sig:accessibility
    Affects accessibility (screen-readers, keyboard navigation, etc)
  • sig:bug
    Incorrect behavior - Breaks a contract/expectation that has been set by the product
  • type:request
    The submitter has identified an issue and is requesting that others provide capacity
  • Concept approved
    Conceptual agreement that a patch on the issue would be accepted (if of sufficient quality)
  • needs:concept approval
    Issue currently pending confirmation that a patch for it would be acceptable
  • type:proposal
    The submitter is working toward change (providing capacity) but wants to get feedback/support
  • triaged
    Issue has had first level triage
  • sig:compatibility
    Affects compatibility with some environment/configuration/version
  • Doing
  • To Do
  • prioritised
    Designated as a priority for product mtce team to work on
  • regression
    A problem which was demonstrably introduced by a recent change (last few months)
  • needs:testing
    A solution has been drafted - but it needs more review/testing