Labels can be applied to issues and merge requests. Group labels are available for any project within the group.
Labels
-
Due to external factors or other issues, this issue can currently not be advanced/worked on
-
This issue contains details or documentation regarding contracts (e.g. for a software license) or the communication related to contracts or acquisitions
-
Issues connected to necessary documentation or that are part of documentation themselves
-
Priority of the issue representing its relevance/necessity - This issue is absolutely necessary for the project and failure to address it might compromise the project
-
Priority of the issue representing its relevance/necessity - This issue would be "nice-to-have"
-
Priority of the issue representing its relevance/necessity - This issue would be very useful and should be worked on, but is not absolutely necessary
-
Issue is currently in the backlog and will/might be pulled into the To-Do-List, depending on urgency, priority and possible workload
-
Issue is done and can be briefly discussed or documented before being closed
-
Issue is part of the current To-Do list: Issues that should be worked on in the immediate future.
-
Structural improvement of the code that does not change functional behaviour.
-
Denotes issues with (potential) security/safety implications or risks
-
These Issues are potentially already completed - A category Label to help with the sorting process of issues
-
This issue needs more information or help from someone outside of the Tech Team - A category Label to help with the sorting process of issues
-
This issue needs to be updated or checked if it still applies - A category Label to help with the sorting process of issues
-
This Issue is potentially no longer relevant or applicable - A category Label to help with the sorting process of issues
Prioritized