How do you assess the severity of a discovered bug?

The severity of a bug is assessed based on its impact on the functionality, stability, and usability of the product. The following categories are typically used:

• Blocker: Completely blocks the operation of a key functionality or the entire application, with no workarounds.
• Critical: Significantly affects the main functionality, leads to crashes, data loss, but may have partial workarounds.
• Major: Affects secondary functionality or causes inconvenience during use, but the main use scenarios are not disrupted.
• Minor: Small flaws that do not affect functionality, such as typos or interface elements that are slightly misaligned.
• Trivial / Cosmetic: Purely visual or textual errors that do not affect the operation of the application.

When assessing, consider:

• The part of the application where the bug was found (module criticality).
• Frequency of the bug occurrence.
• Number of affected users.
• Possibility to bypass the problem.
• Impact on business processes/security.