Most of the system is functioning correctly; it has a low impact or is just aesthetical. We use this severity level to list minor bugs, which we will fix when convenient.

This severity level is the default one; it means the primary functionality is not influenced, or a simple workaround is available.

Please specify. If you are not able to specify, add a comment with @name (who should help to specify it).

A bug related to required compatibility between applications and backend systems or supported OSes, devices, or browsers.

Errors that make the software behavior not compliant with the declared functional requirements. Examples: the app is crashing, a button is not working, or the application shows an unexpected error.

These bugs cause significant performance degradation and lead to poor user experience or low system throughput.

A flaw or vulnerability in the software or hardware design that can be potentially exploited by the attackers

Visual bug related to misaligned, overlapping, or cut of elements; if the bug prevents a functionality, it is a functional bug. Take into account that here is a Wording bug type as well.

Please specify. If you are not able to specify, add a comment with @name (who should help to specify it).

Relates to a missing or incorrect text/content or translation. The Wording type is separate from the UI bug, as it requires a different kind of fix (resources), and another team might fix this in the future.

It is an obvious bug occurring in the primary use cases, every user will most likely notice it. This type of bug might hurt our reputation.

A bug buried in advanced screens that current customers are not heavily using.

This is the default bug visibility rating. The bug is present in non-major functionality, or it is not apparent; users might not care too much, or it is not too embarrassing.

Please specify. If you are not able to specify, add a comment with @name (who should help to specify it).

This Epics needs to be rewritten into smaller parts

This label is used as a filter in development board (so that management tasks are hidden); !=Client Projects

??? Do we want to use this label?

??? Do we want to use this label?

This issue is related to a bug discovered in our application's released version. We use this label to filter bugs out of all the other GitLab issues.

Bug-AT indicates a bug that prevents the completion of a Sprint task (Acceptance Testing/AT); it is not related to a released application. We must resolve it in the Sprint, otherwise, we cannot complete a User Story.