Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
Issue life cycle label: These are activities that have been completed
-
This issue needs to be confirmed if this is the intended behavior of the service
-
Catastrophic issue identified - Severe impact, contain breaking workflow/data loss, zero-day/critical security vulnerabilities No workaround and should be fixed as an immediate priority Need to be released as a patch during regular milestone cycle as soon as a fix is available
-
Major issue identified - High impact, might contain breaking workflow/data loss, critical/high security vulnerabilities There is a workaround that exists but should be fixed as the next priority Might need to be released as a patch during regular milestone cycle/N+1 milestone release
-
Serious issue identified - 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 Can be released in N+1 milestone release
-
Minor issue identified - Low impact, no breaking workflow/any workflow, medium/low security vulnerabilities There is a workaround that exists Can be released in N+1 or more milestone releases
-
A task is an issue where developers use to track the ongoing activities, e.g. could be a clean up. Not necessarily a defect or backlog.
-
This MR relates to changes for unit, integration, etc. testing
-
Issue life cycle label: This is where the work is happening
-
Issue life cycle label: Label applied to indicate that issues are confirmed, but no active work are in progress. Pending volunteers to pick up.
-
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 is low impact, no breaking workflow/any workflow, medium/low security vulnerabilities There is a workaround that exists
-
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 issue has been reviewed and confirmed that it is not an issue but rather an intended behavior/operational issue/basic query.
-
This issue requires further information but lack of responses from submitter. Close after inactivity for more than 6 months.
Prioritized