Quality Testing

Quality is delighting customers

Hi All,

Bug Type: High Priority and High Severity

Share your thoughts and explain with examples


Views: 2559

Replies to This Discussion



When the end user is trying to install any application by clicking on setup.exe, if installation doesn't starts or even if installation starts but terminates abruptly and installation procedure fails. Such issues are good examples for High Priority & High Severity bugs. 




In Simple example, if user goes to Login screen(when it is already member) and gives VALID credentials to required fields and system throws exception like Invalid credential.

This bug must be as High PRIORITY and High SEVERITY

Very True...

It is not always possible that High Priority bug has High Severity. Priority is depends on Business side while Severity depends on Technical side.

Hi Zahid,


Could you please explain your above sentence, 'Severity depends on Technical side'  , How? If possible please explain with example.




Hi Ajay,

As said by Zahid,Severity depends on the Technical Side. For example , u had a simple error in Login screen. From UI prepective it may look so simple but for code prepesctive it may affect other working areas and requires lot of code need to be changed.

Like wise Priority depends on the Bussiness Side. For example you have for an error on logon scenario you may give high priority in general. But for a particular client you are working, that scenario may be least bothered. In this case this issue should be low priority.

My point is that Severity is not only at Technical Level but also we can put it at Business Level.
The severity of the bug is the effect it has on the functionality and it will be (in most cases) directly proportional to the effect. That means, the more the functionality is affected, the higher goes the severity. Priority, on the other hand, refers to how soon the bug needs to be addressed for fix.
Therefore, while a crash bug will always be considered highest in terms of Severity, it's Priority can be lower depending on whether that particular functionality is a part of the current release/deliverable or not.
Similarly, if there is a spelling mistake on the home page of a website, or the logo used is not correct, it will be a bug which is lower in severity but higher in priority.

If there is a bug which is high in severity and is affecting an area of the product which is to be delivered in the current release/iteration, it will be high in priority as well. Hence, it will be a High Severity - High Priority bug.

The severity is set by the testing team and priority by PM.
[There can be variations to the above, based on the conventions in place at different organizations.]

If the product name is misspelled on the login screen, that is low severity (because it does not hurt usability). but high priority (because it looks really bad if you don't).


If a certain scenario causes the product to crash badly, it is high severity. But the dev manager might declare it low priority if that scenario is very rare.


The more is hinders the usability of the product, the higher the severity.

The more important it is to fix, the higher the priority.

Often those scores are similar.


Hi All,

I am Vivek Kulkarni from Pune, just joined the group.

I think High Severity and High Priority bugs should be decided on the basis of how much the bug is affecting the application.

If user is not able to move ahead at any stage(page/function) in the application due to any bug(like page crash, database connectivity issues etc.), should be considered as High Severity and High Priority bug.

Best Regards,

Vivek Kulkarni



TTWT Magazine





© 2021   Created by Quality Testing.   Powered by

Badges  |  Report an Issue  |  Terms of Service