Software Bug Priorities. 10 of transactions. High - This bug should be resolved as soon as possible in the normal course of development activity before the software is released.
1 Critical S1 A defect that completely hampers or blocks testing of the product feature is a critical defect. Priority is driven by business value while Severity is driven by functionality. Correctly assigning bug priority is integral to successfully planning a software development life cycle.
A critical bug is extremely rare and should only be used in instances where if.
Though priority may be initially set by the Software Tester it is usually finalized by the Project Product Manager. For example solving a simple cosmetic issue may only take a few hours of work. What are the different bug priority levels. A bug is a very important aspect of a software testing life cycle and priority and severity are the two of the most common attributes assigned to it.
