Provide examples for classification by urgency levels (urgent, priority, trivial) and severity.

• Urgent/Blocking:

  • Inability to log in.
  • Inability to save critically important data (e.g., order, bank transfer).
  • The application crashes immediately after launch.
  • Security issues, such as the ability to access other users' data without authorization.

• High/Major:

  • Frequently used feature does not work (e.g., product search on the website).
  • Business process logic is broken, leading to incorrect results (e.g., incorrect discount calculation).
  • Serious performance issues slowing down the application for most users.
  • Visual defects making part of the interface unreadable or unclickable.

• Medium/Minor:

  • Minor visual defects that do not hinder usage (e.g., incorrect element alignment).
  • Localization issues (typos, incorrect translation).
  • Page URL 404 instead of the expected one.
  • Minor performance issues noticeable only under certain conditions.

• Low/Trivial:

  • Small cosmetic defects that do not affect functionality or usability (e.g., extra space in text).
  • Typos in inconspicuous places (e.g., footer).
  • Minor issues that do not impact user experience and do not violate business logic.

Severity and Priority Ratio:

Severity is determined by the impact of the defect on the system's operation, while Priority is the urgency of fixing it.

Severity	Priority	Example
Blocking	Urgent	Unable to register in the application scheduled to launch tomorrow.
Major	High	Payment form on the online store website does not work.
Major	Medium	The total amount displayed in the cart is incorrect, but it is correct during checkout.
Minor	Low	Typo in the site's reference section.