Bug triage process

Bug Triage Process:

Triage is a medical term and It refers to dividing sick people into three categories such as: those who will die no matter what you do, those who will recover even if unaided, and those who will recover if only aided.

A bug triaging meeting should be held regularly during the development phase or testing cycle of a Project. The QA lead calls these meetings and goes through all open bugs based on severity and priority.

What should be involved while triaging the bug?

• ·         Check that enough information is provided by QA or not in the defect report so that Dev can understand the defect otherwise triage team can reassign to the QA to provide more information.
• ·         Check if defect is logged under correct project, module and release or not.
• ·         Check whether defect is reported with sensible priority and severity or not.
• ·         Bug Triaging process divides all open bugs into three categories such as bugs to fix now,   bugs to fix later and bugs we will never fix.

Deciding which defect to address:

When there are many open defects logged by QA then developer should not fix the defects randomly. Now you have a question in your mind that which defects should be fixed by developers first. So answer to your question is based on assigned priority and severity of the bug.

There are other following reasons to triage the bugs which needs to be address first

• ·         What is the impact on end customer because of open defect?
• ·         What is the possibility/Probability to hit the bug in production by the customer?
• ·         What is the functional impact because of the open bug?
• ·         Is that bug fix regression prone? What level of testing is required for bug fix?
• ·         What it the technical challenges to address the bug?