Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
risk treatmentacceptGitLab.orgThe vulnerability is accepted (often due to very low risk) and it will not be fixed.
-
risk treatmentfalse positiveGitLab.orgThe vulnerability was incorrectly reported and is not actually present or exploitable in any way.
-
risk treatment::mitigate severityacceptGitLab.orgThe severity level downgraded because compensating controls in place AND the risk is accepted (i.e. will not be fixed).
-
risk treatment::mitigate severityremediateGitLab.orgThe severity level should be downgraded due to compensating controls in place.
-
risk treatmentoperational requirementGitLab.orgThe issue is not able to be remediated due to technical constraints. This state will keep the issue open until it is able to be remediated in the future.
-
risk treatmentremediateGitLab.orgThe vulnerability will be remediated and an exception request is not required
-
roadmaplaterGitLab.orgRoadmap items with low certainty but that we think we want to do in the future.
-
roadmapsGitLab.orgCategory vision in Plan stage: https://about.gitlab.com/direction/plan/portfolio_management/
-
safe-to-retryGitLab.orgThis label was created by group::database to indicate MRs that are safe to retry, specifically around PK migration MRs
-
samlGitLab.orgIssues related to integration with SAML: http://doc.gitlab.com/ce/integration/saml.html
-
scaled migrationsGitLab.orgFor issues related to large migrations performed by our importers. This should only be used by group::import and integrate
Prioritized