Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
This defect indicates complete shut-down of the process, nothing can proceed further and constitutes a breaking defect
-
This defects is a major issue but certain parts of the system remain functional.
-
This defect has medium impact, no breaking workflow/no data loss, high/medium security vulnerabilities There is a workaround that exists and should be fixed after high priority
-
This defect is low impact, no breaking workflow/any workflow, medium/low security vulnerabilities There is a workaround that exists
-
This issue requires further information but lack of responses from submitter. Close after inactivity for more than 6 months.
-
This label indicates that the issue is a duplicate and there has been a related issue created
-
This label is used to indicate cherry picks into previous releases for fixing an issue, this is for backporting patches in up to N-2 releases.
-
An enhancement may be made to address specific user needs or requests, or they may be made to address broader goals, such as increasing the efficiency or effectiveness of the software. May or may not require an ADR depending on the nature of the change. This applies to improving or enhancing existing software behavior only, without introducing new features.
-
Merge request label for indicating work related to internal audit, logging, reporting improvement
-
Merge request related to an enhancement or upgrade of the existing code, increasing the efficiency or effectiveness of the software without necessarily introducing new features to end user.
-
Merge request label for indicating initial development of a project
-
Issue regarding work related to code clean ups/refactoring/optimization
-
Merge request label for indicating code deprecation, will need to include this in the release notes
-
This backlog item / Issue / MR affects the community reference implementation
Prioritized