Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
it-service deskCSIGitLab.comIT Department. Continual Service Improvement issue. Ongoing process that focuses on improving the quality of services and the efficiency of IT processes.
-
it-service deskchange requestGitLab.comIT Department. Formal proposals for modifying the IT infrastructure, services, or any other configuration item. Changes are more substantial than Service Requests and require a formal assessment, authorization, and planning process to mitigate potential risks and impacts.
-
it-service deskincidentGitLab.comIT Department. An unplanned interruption or reduction in the quality of an IT service. It can also refer to the failure of a configuration item (CI) that has not yet impacted service but poses a significant risk of doing so in the future. Examples: bugs, application crash, server failure, data loss, service unavailability, etc.
-
it-service deskservice requestGitLab.comIT Department. Routine and predefined requests from users for access to specific IT services or information. These requests are typically low-risk and frequently occurring, and they follow predefined procedures for fulfillment. Examples: Request for password reset, request for software installation, request for software configuration changes.
-
it-servicearchieGitLab.comIT Department. Access Request Configuration Hyperautomation Identity Engine (ARCHIE)
-
it-serviceawsGitLab.comIT Department. Applied to all AWS infrastructure related issues that are not specific to the GitLab Sandbox Cloud.
-
it-servicedemo-systemsGitLab.comIT Department. Applied to all Customer Success Demo Systems related issues.
-
it-servicegcpGitLab.comIT Department. Applied to all Google Cloud Platform (GCP) issues that are not specific to the GitLab Sandbox Cloud.
Prioritized