Labels
Prioritized labels 25
Drag to reorder prioritized labels and change their relative priority.
-
Category:ServerlessGitLab.orgAll issues and MRs related to the Serverless category within devops::configure. https://about.gitlab.com/direction/configure/serverless/
-
dockerfileGitLab.org / GitLab Docs DEPRECATEDRelated to the dockerfiles present in the gitlab-docs project
-
Category:Chaos EngineeringGitLab.orgIssues related to chaos engineering (part of ~devops:configure stage)
-
devopsconfigure [DEPRECATED]GitLab.org[DEPRECATED] should use devops::deploy now. Issues for the Configure stage of the DevOps lifecycle (e.g. Auto DevOps , Kubernetes Configuration, ChatOps, Serverless, PaaS)
-
Category:Infrastructure as CodeGitLab.orgAll issues and MRs related to the Infrastructure as Code category within devops::configure. https://about.gitlab.com/direction/configure
-
[deprecated] Accepting merge requestsGitLab.org[deprecated] Please use "Seeking community contributions" instead. gitlab-org/developer-relations/contributor-success/team-task#77
-
Category:Cluster MonitoringGitLab.orgIssues belonging to the Monitor stage Health group for product category Cluster Monitoring
-
Category:Auto DevOpsGitLab.orgIssues for Auto DevOps, part of the Configure stage of the DevOps lifecycle
-
Category:Code QualityGitLab.orgAll issues and MRs related to the Code Quality category. See https://about.gitlab.com/direction/secure/static-analysis/code-quality/
-
Category:Container RegistryGitLab.orgCategory label - Features that apply to management container registries
-
groupconfigure [DEPRECATED]GitLab.org[DEPRECATED] should use group::environments. Issues belonging to the Configure group of the Configure stage of the DevOps lifecycle. See https://about.gitlab.com/handbook/product/categories/#configure-group
-
Category:Continuous IntegrationGitLab.orgAll issues and MRs related to the continuous integration category within devops:verify https://about.gitlab.com/direction/verify/continuous_integration
-
infrastructure configurationGitLab.orgIssues for Infrastructure Configuration, part of the Configure stage of the DevOps lifecycle
-
Category:Cluster Cost OptimizationGitLab.orgIssues related to the "cluster cost optimization" category of the configure stage. See &503
-
Category:Cloud Native InstallationGitLab.org
-
development guidelinesGitLab.orgChanges or updates to the development guidelines in the /development directory in the GitLab documentation. (Info: https://docs.gitlab.com/ee/development/)
-
groupsource codeGitLab.orgIssues belonging to the Source Code group of the Create stage of the DevOps lifecycle. See https://about.gitlab.com/handbook/product/categories/#source-code-group
-
grouprunner coreGitLab.orgIssues belonging to the Runner group of the Verify stage of the DevOps lifecycle.
-
Category:Kubernetes ManagementGitLab.orgRelating the `Kubernetes Management` category within the configure stage
Labels 3,627
-
FedRAMP MilestoneRAR RequirementGitLab.orgRequired for Readiness Assessment (our first compliance assessment). **Do not remove this label without coordinating with FedRAMP PM and Compliance. Questions: #wg_fedramp**
-
FedRAMP MilestoneRequired for SARGitLab.orgNeeds to be complete for Security Assessment. See timeline in https://internal-handbook.gitlab.io/handbook/engineering/fedramp-compliance/#key-milestones. **Do not remove this label without coordinating with FedRAMP PM and Compliance. Questions: #wg_fedramp**
-
FedRAMP WorkflowNeeds Compliance inputGitLab.orgNext step: clarification or information from Compliance
-
FedRAMP WorkflowNeeds PM triageGitLab.orgNext step: FedRAMP Product Manager updates, reviews, moves, or closes this issue
-
FedRAMP WorkflowNeeds group inputGitLab.orgNext step: product group or subject matter expert reviews issue and identifies next steps
-
FedRAMP WorkflowOut of scopeGitLab.orgFedRAMP PM and Compliance have determined this issue is not required to satisfy FedRAMP controls. (It may be needed for other reasons.) Only FedRAMP PM or Compliance should apply this label.
-
FedRAMP WorkflowReady for implementationGitLab.orgNext step: implement the change. This indicates that no further FedRAMP control analysis is currently required.
-
FedRAMP::DR StatusAcceptedGitLab.orgThis issue has been identified as a vulnerability that has completed and accepted by the PO&AM Vulnerability Deviation Request Process. The team does not need to perform any further action.
-
FedRAMP::DR StatusDeniedGitLab.orgThis issue has been identified as a vulnerability that has completed and denied by the PO&AM Vulnerability Deviation Request Process. The team must resolve this.
-
FedRAMP::DR StatusOpenGitLab.orgThis issue has been identified as a vulnerability that has started the PO&AM Vulnerability Deviation Request Procedure
-
FedRAMPVulnerabilityGitLab.orgApply label to container scan vulnerabilities of FedRAMP/FIPS images https://internal-handbook.gitlab.io/handbook/engineering/infrastructure/platforms/gitlab-dedicated/us-public-sector-services/architecture/fedramp-boundary-vulnerability-scanning/. Previously titled as FedRAMP Milestone::Vuln Remediation
-
FedRampWaiting on VendorGitLab.orgNext Step: Wait for vendor to issue fix, ensure to checkin with vendor every 30 days. Open DR request if near breach.
-
FillerGitLab.orgIssues that are fillers for the current milestone in case the team completes their deliverables early