Labels can be applied to issues and merge requests. Group labels are available for any project within the group.
Labels
-
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
-
type:paid-issue-queueLabel used to identify fixes and improvements that are prioritized by the core team and funded by the community.
-
type:backlogThe submitter has documented an issue but does not expect immediate action.
-
triagedIssue has had first level triage
-
sig:usabilityThe issue affects the intuitiveness or productivity of casual users
-
sig:unverified-bugBug needs to be confirmed on latest version
-
sig:translationAffects support for multiple languages or locales
-
sig:sysadminThe issue affects the manageability or productivity from the sysadmin perspective
-
sig:security-improvementThe issue improves security functionality (eg more permissioning or cryptography options). Do NOT file a vulnerability/exploit here.
-
sig:performance(Significance) Affects how *quickly* the system runs
-
sig:maintainabilityAffects maintainability, code-quality, testability, quality-assurance, etc
-
sig:leximIndicates an issue whose fix is helpful on our path to renewal via form builder/apiv4 & other leaps
-
sig:legacy-uiIndicates bug relates to a part of the UI we anticipate being replaced by the form builder approach
-
sig:compatibilityAffects compatibility with some environment/configuration/version
-
sig:bugIncorrect behavior - Breaks a contract/expectation that has been set by the product
-
sig:accessibilityAffects accessibility (screen-readers, keyboard navigation, etc)
-
regressionA problem which was demonstrably introduced by a recent change (last few months)
-
prioritisedDesignated as a priority for product mtce team to work on
-
needs:testingA solution has been drafted - but it needs more review/testing
Prioritized label