Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
AccessibilityInformation Services / DevOps
-
Business AnalysisIssues which ask questions about an existing business process or which require the development of a new oneInformation Services / DevOps
-
choreIssues where the work required is "straightforward" (such as fixing typos, manually configuring a service), usually time-boxed to half-a-dayInformation Services / DevOps
-
Comms RequiredCommunication required to release featureInformation Services / DevOps
-
dependencyInformation Services / DevOps
-
design neededIssues which cannot be addressed without some design work being carried outInformation Services / DevOps
-
DevelopmentIssues which require active software or infrastructure-as-code development workInformation Services / DevOps
-
discussionIssues which primarily contain or require a discussion rather than a taskInformation Services / DevOps
-
DocumentationIssues which require writing documentation for the team or end usersInformation Services / DevOps
-
EpicTypeEpicThe most detailed type of epic - issues are attached to epics at this levelInformation Services / DevOps
-
EpicTypeFeatureMid-level epicInformation Services / DevOps
-
EpicTypeInitiativeUsed for grouping detailed epics for easier managementInformation Services / DevOps
-
good first issueInformation Services / DevOps
-
incompleteIssue is incomplete and needs its description improvingInformation Services / DevOps
-
issueTypeBugFunctionality of product is not as designed or intended by the code authorInformation Services / DevOps
-
issuetypeEpicInformation Services / DevOps
-
issuetypeFeedbackFor feedback on the system provided by usersInformation Services / DevOps
-
issuetypeSupportInformation Services / DevOps
-
issuetypeTaskInformation Services / DevOps
-
issuetypeThemeThis is a large collection of work, comprised of one or more epicsInformation Services / DevOps
Prioritized label