Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels 104
-
Business AnalysisInformation Services / DevOpsIssues which ask questions about an existing business process or which require the development of a new one
-
choreInformation Services / DevOpsIssues where the work required is "straightforward" (such as fixing typos, manually configuring a service), usually time-boxed to half-a-day
-
communal-benefitInformation Services / DevOpsIssues which are of benefit to multiple teams but the direct responsibility of none. All teams should consider these issues in sprint planning.
-
design neededInformation Services / DevOpsIssues which cannot be addressed without some design work being carried out
-
Developer ExperienceInformation Services / DevOpsIssue relates to developer tooling or documentation
-
DevelopmentInformation Services / DevOpsIssues which require active software or infrastructure-as-code development work
-
discussionInformation Services / DevOpsIssues which primarily contain or require a discussion rather than a task
-
DocumentationInformation Services / DevOpsIssues which require writing documentation for the team or end users
-
EpicTypeEpicInformation Services / DevOpsThe most detailed type of epic - issues are attached to epics at this level
-
EpicTypeInitiativeInformation Services / DevOpsUsed for grouping detailed epics for easier management
-
EpicTypePlaceholderInformation Services / DevOpsTo capture anticipated work while allowing it to be filtered out of epic lists/boards
-
incident-remedialInformation Services / DevOpsWork derived from past incidents (e.g. degradation of service) that aims to help avoid future incidents. This can be both symptom/short term geared, like improving SQL queries efficiency of an API call or root cause/long term geared, like reporting SQL queries stats or load tests.