Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
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
-
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
-
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
-
This issue needs to be confirmed if this is the intended behavior of the service
-
Issue life cycle label: These are activities that have been completed
-
A defect is an issue that is a software error, flaw or fault that causes that project or repo or service to produce an incorrect or unexpected result per the OSDU standard or requirements or that it behaves in unintended ways. A defect can be further categorized as a defect in the common code in the PMC project or as a defect within the CSP realization of the PMC project to ensure that it can be targeted towards the right development resource to address this issue.
Prioritized