Labels
Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels 3,539
-
SecDepartmentSecurity AssuranceGitLab.comLabel for the Security Assurance Department: https://about.gitlab.com/handbook/security/security-assurance/
-
SecResearch FollowupEcosystemGitLab.comFor issues created as followup from Security Research ecosystem security projects
-
SecResearchWorkTypeCodeReviewSessionGitLab.comUsed by Security Research team to perform code review sessions.
-
SecResearchWorkTypeTSVGitLab.comUsed by Security Research team to perform technical security validation (TSV) work. See https://handbook.gitlab.com/handbook/security/security-assurance/technical-security-validation/#tsv-workflow for more details
-
Security Alert - Customer CommunicationsGitLab.comThis label is to be applied to new issues related to security communications being co-worked on by MktgOps. Label is connected to a Workato flow to notify mktgops slack channel
-
Security ArchitectureGitLab.comLabels something that is interesting for the Security Architecture team https://handbook.gitlab.com/handbook/security/product-security/security-platforms-architecture/security-architecture/
-
Security HackathonGitLab.comThis is a label for issues/epics participating in the upcoming Security Hackathon event
-
SecurityPMGitLab.comApplied to assist the SecurityPM in tracking issues that cross departments and teams - contact DRI: Will Szabo
-
Security_Thought_LeadershipGitLab.comSecurity department thought leadership (blogs, articles, podcasts, interviews etc)