What is low priority and low severity bug?
Robert Miller
Published Mar 16, 2026
What is low priority and low severity bug?
Bug Severity vs Priority
| Bug Severity | Bug Priority |
|---|---|
| High severity and low priority status means that the bug can cause significant damage, but can be fixed at a later date | High priority and low severity status means that the bug must be fixed immediately but it does not affect the software too adversely |
What is the example of high severity and low priority?
For example: If an application or web page crashes when a remote link is clicked, in this case clicking the remote link by an user is rare but the impact of application crashing is severe. So the severity is high but priority is low.
What is severity and priority of bug give some example?
In other words it defines the impact that a given defect has on the system. For example: If an application or web page crashes when a remote link is clicked, in this case clicking the remote link by an user is rare but the impact of application crashing is severe. So the severity is high but priority is low.
Can there be a defect with low severity and high priority?
Example of Defect Severity and Priority A very low severity with a high priority: A logo error for any shipment website, can be of low severity as it not going to affect the functionality of the website but can be of high priority as you don’t want any further shipment to proceed with the wrong logo.
What is low severity?
Low Priority, Low Severity :- Any cosmetic or spelling issues which is within a paragraph or in the report. High Priority, High Severity :- An error which occurs on the basic functionality of the application and will not allow the user to use the system (E.g. user is not able to login to the application)
What is the difference between severity and priority of the bug?
Bug Severity is the degree of impact that a defect has on the system; whereas, Bug Priority is the order of severity which has impacted the system. Severity is related to standards and functionality of the system; whereas, Priority is related to scheduling.
Who will decide priority and severity?
Priority is typically decided in consultation with the project manager, whereas the tester determines the severity level. Once the priority level and the severity of the system defect is understood by all, further action can be implemented.
What is critical bug?
Critical (#) Bug (#) Critical bugs include those that: Render a site unusable and have no workaround. Cause loss/corruption of stored data. (Lost user input, e.g. a failed form submission, is not the same thing as data loss and in most cases is major).
What is the difference between bug priority & bug severity?
What is bug severity and priority?
Severity means how severe defect is affecting the functionality. Priority means how fast defect has to be fixed. Severity is related to the quality standard. Priority is related to scheduling to resolve the problem.
How do you determine the severity of a bug?
Bug Severity is determined by Quality Analyst, Test engineer; whereas, Bug Priority is determined by the Product Manager or Client.
What is priority and severity for a defect give a few examples of high priority and high severity defects?
Severity vs Priority
| Severity | Priority |
|---|---|
| If the Priority of a defect is high and the severity is low, then, the defect must be fixed immediately. | If the Severity of a defect is high and the Priority is low, then, the defect must be fixed but not immediately. |