Priority of defect

Priority:

             Priority means the importance and urgency to fix the defect by the developers (i.e.) which defect should be fixed first and which should be fixed in later versions.

Def:    Defect Priority (Bug Priority) indicates the importance or urgency of fixing a defect. Though priority may be initially set by the Software Tester, it is usually finalized by the Project/Product Manager.

Priority Levels:

• Low
• Normal
• High
• Urgent
• Immediate

Immediate: Must be fixed the defect immediately. needs to be fixed ASAP, a week at the most

Urgent: Must be fixed the defect in the next build. should be fixed within the next month

High: Must be fixed the defect in any of the upcoming builds but should be included in the release.

Normal: May be fixed the defect after the release / in the next release. should be fixed in this quarter, or by the next release

Low: May or may not be fixed at all. should get to this within 6 months, or the release after next