Importance Matrix

Importance is the combination of a bug's Priority, Severity, Services Priority, and Business Priority. Bugzilla does not automatically calculate Importance, as it is a judgement made by individuals who are responsible to resolve the bug.

*Severity Priority Services Priority Business Priority
Set by Reporter.
*Required to open a bug 		Set by a member of a development team.
Priority may suggest the order the developer will work on bugs. 		Set and used by Services.
Services Priority indicates Services' judgement of the bug's priority.
NOTE: All bugs related to an SR should have a Services Priority. 		Set and used by IS&T.
NOTE: This value is integrated in the IT Ops Review Portlet in Clarity.
Critical: Crash, data loss or corruption, severe memory leak, etc.
Major: Major loss of function
Normal: Regular issue, some loss of functionality under specific circumstances
Minor: Trivial, e.g. cosmetic, UI, easy work around
Enhancement: Request for new, additional functionality 		P0: Customer Critical Situation
P1: Urgent
P2: High
P3: Medium
P4: Low
P5: None (default/unassigned) 		1: Highest priority (most important)
1,000: Lowest priority (least important) 		None: not reviewed or assigned
1-99: Project Queue: Priority for a project bug.
100-149: Working Queue: Priority for bugs to be worked on now.
150-199: Up-Next Queue: Priority for a bug to get worked on if the developer has time.
200-499: BA Queue: Priority for bugs the BA should work on. NOTE: Not used.
600-699: Sys Admin Queue: Priority for bugs the System Administrator should work on. NOTE: Not used.
800-999: Holding Queue: Priority for bugs to be addressed in the future. Typically, these are anything from minor enhancements to projects.