A subjective rating of the bug as it relates to the business or customer requirements. Priority indicates the order in which code defects should be fixed. You can specify the following values:
- Product cannot ship without the successful resolution of the work item, and it should be addressed as soon as possible.
- Product cannot ship without the successful resolution of the work item, but it does not need to be addressed immediately.
- Resolution of the work item is optional based on resources, time, and risk.
A subjective rating of the impact of a bug on the project or software system. For example: If clicking a remote link (a rare event) causes an application or web page to crash (a severe customer experience), you might specify Severity = 2 - High and Priority = 3. Allowed values and suggested guidelines are:
- Critical: Must fix. A defect that causes termination of one or more system components or the complete system, or causes extensive data corruption. And, there are no acceptable alternative methods to achieve required results.
- High: Consider fix. A defect that causes termination of one or more system components or the complete system, or causes extensive data corruption. However, an acceptable alternative method exists to achieve required results.
- Medium: (Default) A defect that causes the system to produce incorrect, incomplete or inconsistent results.
- Low: A minor or cosmetic defect that has acceptable workarounds to achieve required results.