Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
Importance: 7
-
Importance: 8
-
Importance: 9
-
Other: UpstreamThis issue should be fixed/implemented in the upstream repository
-
Severity: CriticalThe defect affects critical functionality or critical data. It does not have a workaround. Example: Unsuccessful installation, complete failure of a feature.
-
Severity: MajorThe defect affects major functionality or major data. It has a workaround but is not obvious and is difficult. Example: A feature is not functional from one module but the task is doable if 10 complicated indirect steps are followed in another module/s.
-
Severity: MinorThe defect affects minor functionality or non-critical data. It has an easy workaround. Example: A minor feature that is not functional in one module but the same task is easily doable from another module.
-
Severity: TrivialThe defect does not affect functionality or data. It does not even need a workaround. It does not impact productivity or efficiency. It is merely an inconvenience. Example: Petty layout discrepancies, spelling/grammatical errors.
-
Status: Cannot-ReproduceThe defect cannot be reproduced.
-
Status: Code-ReviewThe issue is under peer code review.
-
Status: DiscussionThe issue is being discussed by the team/community
-
Status: Info-NeededAdditional information needed to proceed with the issue
-
Status: In-ProgressThe issue is in development.
-
Status: New/SuggestionNew suggestion to build a feature/user story, product enhancement, bug etc.
-
Status: PostponedPostponed until some condition is met (see issues comments)
-
Status: QAThe issue is fixed/implemented and is waiting for approval from the QA team.
-
Status: Ready-For-DevA developer can start working on this task
-
Story: Bug
-
Story: EpicLarge body of work that can be broken down into a number of smaller stories
-
Story: Research
Prioritized label