Who in the team was responsible for setting priorities and defect importance?

Priorities and severity of defects were established during joint meetings of the development and QA teams, with the participation of the product manager or business analyst.

Roles and responsibilities:

• QA Engineer: Detected the defect, provided a detailed description, reproduction steps, expected and actual results, and offered an initial assessment of importance from the user's perspective.
• Developer: Analyzed the technical complexity of fixing and the potential impact on other parts of the system.
• Product Manager / Business Analyst: Assessed the business impact of the defect, its effect on users, and its alignment with product priorities.

The final decision on priority was made jointly, considering all these factors. In case of disagreements, the final say was with the product manager or team lead.

Prioritization is based on a matrix considering:

Priority	Severity	Impact on business and users
Blocker	Critical	Blocks key functionality, makes the application inoperable. Requires immediate fixing.
High	Major	Seriously disrupts the operation of important functionality, but workarounds exist. Affects a large number of users.
Medium	Minor	Slightly worsens the operation of functionality, simple workarounds are available. Noticeable to users.
Low	Trivial	Cosmetic errors, insignificant impact on functionality. Does not affect most users.

Severity is a technical assessment of the impact of the defect on the system, set by QA and sometimes by developers. Priority is a business decision on how quickly the defect should be fixed, established jointly with the product manager. These two parameters may not coincide.

Tools for defect tracking (e.g., Jira) were used for recording and discussing priorities.