Labels can be applied to issues and merge requests. Group labels are available for any project within the group.
Labels
-
The submitter has identified an issue and is requesting that others provide capacity
-
The submitter is working toward change (providing capacity) but wants to get feedback/support
-
Label used to identify fixes and improvements that are prioritized by the core team and funded by the community.
-
The submitter has identified a complex problem-area. The issue may require discussion or exploration. The issue may lead to other filings, but it may not have a direct resolution of its own.
-
The submitter has documented an issue but does not expect immediate action.
-
The issue affects the intuitiveness or productivity of casual users
-
The issue affects the manageability or productivity from the sysadmin perspective
-
The issue improves security functionality (eg more permissioning or cryptography options). Do NOT file a vulnerability/exploit here.
-
Affects maintainability, code-quality, testability, quality-assurance, etc
-
Indicates an issue whose fix is helpful on our path to renewal via form builder/apiv4 & other leaps
-
Indicates bug relates to a part of the UI we anticipate being replaced by the form builder approach
-
Affects compatibility with some environment/configuration/version
-
Incorrect behavior - Breaks a contract/expectation that has been set by the product
-
Affects accessibility (screen-readers, keyboard navigation, etc)
-
A problem which was demonstrably introduced by a recent change (last few months)
Prioritized