Bug Triage Meetings (sometimes called Bug Councils) are project meetings in
which open bugs are divided into categories. The most important distinction is
between bugs that will not be fixed in this release and those that will be

There are three in software - bugs to fix now bugs to fix later and bugs we
will never fix.

Triaging a bug involves:

Making sure the bug has enough information for the developers and makes sense.

Making sure the bug is filed in the correct place.

Making sure the bug has sensible Severity and Priority fields

Bug Triage is the process of evaluating defect reports to determine their course of action.

It is typically the Program Manager's (PM) responsibility to facilitate a meeting (called Bug Triage) with expert members from the business sector development and test in attendance. Together they assess the status of defects and forward associated reports to appropriate individuals so they can take further action. For example defect reports are routed to the business analyst when problems appear to be due to unclear or incomplete requirements. Likewise defect reports are routed to developers when problems appear to be caused by improper source code. The PM may 'Close' the defect if there is reason to believe it isn't justified. The PM normaly has the last word as to how the bug will be handled.