Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels 3,603
-
Speakers-CommunityGitLab.comEvents with strict rules around CFP and Sales pitches often lead to disqualification. e.g. KubCon.
-
Speakers-LightningTalksGitLab.comEvents where GitLab will be hosting Lightning Talks, and we will invite both internal and external speakers.
-
Speakers-ProductGitLab.comThese are events where we will mainly talk about GitLab and sales pitches are allowed.
-
StORMAdd to ZenGRCGitLab.comThe Security Risk Team has performed a StORM Risk Assessment and needs to add this risk to ZenGRC.
-
StORMBlockedGitLab.comNo further action can be performed. Support is required. Assignee should be the individual on point for escalation.
-
StORMIntakeGitLab.comLabel to communicate potential security operational risks to the Security Risk Team
-
StORMNeeds Additional InformationGitLab.comAdditional information is required to support the Security Risk Team's StORM Risk Assessment
-
StORMNot StartedGitLab.comThis label indicates that the associated issue is ready to be actioned. The owner should be the person on point.
-
StORMOut of ScopeGitLab.comThe Security Risk Team performed a StORM Risk Assessment and determined that the potential risk identified is out of scope for the StORM program because it is not considered an operational security risk.
-
StORMQAGitLab.comIssues (such as Risk Treatment) requiring manager or peer review should be added to this label and assigned to the reviewer prior to closure.
-
StORMScheduledGitLab.comSecRisk utilizes this label to identify issues that have a due date but do not require action from Security Engineers at this time (such as risk treatments).