Bug Triaging

Bug Triaging [also called as Bug council]
Bug Triaging is a project meeting on bugs in the project,where the open bugs are classified as follows
- Bugs to fix now
- Bugs to fix later
- Bugs that will never be fixed

There is a secondary purpose of bug triaging in checking
- The bug are valid,they have correct description for developers and other team member to understand it
- The mentioned bugs are at the right place to track
- The Priority and Severity levels associated with a bug are appropriate w.r.t the upcoming and future releases
Something on Priority and Severity,
The best statement that explains it would be "Priority is business while Severity is Technical"

Assigning Severity is a straightforward approach, Severity implies how serious the identified/discovered issue is? It in a way explains the technical offset from the specification and its degree.

Assign Priority is more of business focused approach. Priority implies how important it is for the business/client that the bug be fixed.

Scales:
Priority Scales: Many companies use their own scale to define this , However they are all on same lines
3- Point Scale
1. P1/ High/Must fix as soon as possible
2. P2/Medium/ Fix soon , maybe next release
3. P3/ Low/ Fix later when we have sufficient time

Severity Scales :
3- point scale is similar to the one mentioned above , but there is variation in 5-point scale
5 - Point Scale
1. Blocking/Critical/P1-Crash [Data crash,application crash,Blocking path or Major functionality missing or wrong ]
2. Major/P2 [Major functionality not implemented properly, Give errors on certain cases ]
3. Medium/P3 [Functionality missing at certain scenario or gives wrong results]
4. Minor / P4 [Issues with UI, alignment, System fails for a negative test case or for an unrealistic scenario]
5. Trivial/Cosmetic / P5 [Issue being too trivial or of just an observation type ]