Common sense should always have precedence over this rules. But to have some commonality between assigning bugs priorities, use the following guidelines.

•Low impact

This is for Minor problems, such as failures at extreme boundary conditions that are unlikely to occur in normal use, or minor errors in layout/formatting. These problems do not impact use of the product in any substantive way.

•Medium impact

This is a problem that a) Affects a more isolated piece of functionality. b) Occurs only at certain boundary conditions. c) Has a workaround (where "don't do that" might be an acceptable answer to the user). d) Occurs only at one or two customers. or e) Is very intermittent

•High impact

This should be used for only serious problems with no workaround. Frequent or reproducible crashes/core dumps/GPFs would fall in this category, as would major functionality not working.

•Urgent impact

This should be reserved for only the most catastrophic of problems. Data corruption, complete inability to use the system, etc.