The issue represents a bug that needs to be resolved.

Indicates that this issue relates to the deployment process.

Indicates that this issue relates to functionality of the pipeline.

Indicates that this issue relates to automated tests.

Indicates an issue that requires a good understanding of a project's structure as a lot of components are effected. Errors made would likely break functionaliy for a lot of components.

Indicates a low complexity issue that should be completed easily.

Indicates an issue that requires more effort and knowledge to complete.

Code documentation required.

Update or create documentation in the wiki / other outside docs.

The issue should be worked on immediately, as it is required for several other issues.

The issue should be worked on if time permits but can be postponed.

The issue should be worked on in order to complete the required tasks so other issues that may require this functionallity can be worked on.

A problem that results in complete loss of functionality and has no workaround. E.g. application crashes.

Part of the application or software doesn’t do what it’s specifically designed to do; there may be a workaround.

Non-critical functionality of the software is affected, and the issue may have a workaround.

Indicates that this issue is about documentation and not about writing new functionality.

Indicates that this issue is about a general enhancement not necessarily is just about code / documentation updates and therefore not covered by the 'type::update functionality' label.

Indtcates that the functionality described in this issue should be implemented.