Labels can be applied to issues and merge requests. Group labels are available for any project within the group.
Labels
-
To Do
-
Doing
-
triagedIssue has had first level triage
-
Concept approvedConceptual agreement that a patch on the issue would be accepted (if of sufficient quality)
-
epic:ro-dbTied to the overall goal of allowing read-only DB clones
-
type:requestThe submitter has identified an issue and is requesting that others provide capacity
-
type:proposalThe submitter is working toward change (providing capacity) but wants to get feedback/support
-
sig:performance(Significance) Affects how *quickly* the system runs
-
regressionA problem which was demonstrably introduced by a recent change (last few months)
-
prioritisedDesignated as a priority for product mtce team to work on
-
sig:unverified-bugBug needs to be confirmed on latest version
-
sig:usabilityThe issue affects the intuitiveness or productivity of casual users
-
sig:legacy-uiIndicates bug relates to a part of the UI we anticipate being replaced by the form builder approach
-
type:paid-issue-queueLabel used to identify fixes and improvements that are prioritized by the core team and funded by the community.
-
needs:concept approvalIssue currently pending confirmation that a patch for it would be acceptable
-
needs:steps to replicateAn issue has been identified - but it needs more reliable guidance to reproduce the problem
-
needs:planningAn issue has been identified - but it needs more planning/analysis before taking action
-
needs:documentationA draft solution has been prepared - but it needs documentation for users or developers
-
needs:testingA solution has been drafted - but it needs more review/testing
-
git:civicrm-backdropInvolves source code from the "civicrm-backdrop" git repo
Prioritized label