Labels can be applied to issues and merge requests. Group labels are available for any project within the group.
Labels
-
!Priority::Waiting for OrderDigital TwinThe Epics with this label can't be prioritized since there is not order for client. So the delivery dates are not clear.
-
Agile-State::Backlog RefinementDigital TwinUser Story with this label will be discussed during the Backlog Refinement
-
Agile-State::FailedDigital TwinUser Story with this label failed, because it couldn't be implemented in the way it is written down.
-
Agile-State::MovedDigital TwinThis label means that User Story couldn't be completed in previous Sprint, so it was moved to next one (reason must be specified in comment)
-
Agile-State::US DoRDigital TwinDoR - Definition of Ready, User Story is ready a reviewed, so is valid for Sprint Planning
-
Bug-origin::ExternalDigital TwinUse this Bug Type if a bug is reported by 3rd party (client, customer, etc.), and add the customer/reporter name if possible so that we might follow up if needed.
-
Bug-origin::External-SLADigital TwinReported by 3rd party (client, customer, etc.) under SLA agreement, and we are legally bound to fix it in a pre-agreed time frame - automatically High priority!
-
Bug-origin::InternalDigital TwinUse this Bug Type if we have discovered the bug internally and no customers complain about it yet.
-
Bug-origin::UndefinedDigital TwinPlease specify. If you are not able to specify, add a comment with @name (who should help to specify it).
-
Bug-severity::CriticalDigital TwinSystem Down. Complete system outage. The primary functionality is not working for several customers. Or there is threat of data breach/loss or system exploitation.
-
Bug-severity::MajorDigital TwinA severe downgrade of important functionality/service. It does not impact a customer's business continuity but causes discomfort for a customer; a workaround exists; otherwise, it would be critical.
Prioritized