Bug tickets should be treated as priority unless otherwise approved by management or the project manager. Bug's should be tracked and dealt with as swiftly as possible. Client Satisfaction is negatively affected when bug tickets are not created and addressed properly. This is why the procedure noted above is so important to follow. If the Bug is deprioritized by the client, the priority should be set to "8 - Deferred Bug".
A project manager is required to validate each bug ticket. This means it is the responsibility of each project manager to check the work being done by their developer. This requires actually pulling up the development or staging site and either attempting to reproduce the bug or verify a bug or blockers validity.
It is the responsibility of all Clarity team members to ensure this procedure is adhered to; however, most of the responsibility is on the project manager to ensure this procedure is followed. A good amount of the responsibility is also with the QA engineer, who's responsibility is fail the ticket and put it in the correct sprint.
It is the responsibility of the developer to block a ticket and create an impediment if a bug ticket cannot be worked. The reason the ticket cannot be worked should be documented clearly and concisely in the impediment associated to the failed bug ticket.
Understanding Azure Dev Ops Ticket/User Story Statuses