abd

• Sep 4th, 2013

 

When Severity and Priority is opposite, then we would obviously go by Priority since Priority relates to business.
Eg When Severity is high and Priority is Low then we would defer it and take it up later since is Priority is low.

Severity is low Priority is high then we would take it since the Priority is high.

Niyati

• Sep 16th, 2013

 

I Disagree with this, that only Priority part is affect to business.

B REDDY

• Jul 23rd, 2014

 

Severity means how serious is the issue(Ex: One application everything is there login and password. But click option is not enable. This is the severity of the issue

Priority: Means based on the priority(Critical,High, Medium,Low) we will resolve the issue. But all critical issues cannot be most priority issues sometimes.
Low priority issues also might be critical
Ex: Application Graphics is not good. This is also considered Severity

hash

• Dec 15th, 2014

 

i agree with Niyati, Priority will be decided by business. Business may say they would want a defect to be fixed first and that might not have SEV1 from tester perspective. Priority is the order in which business wants to get the defects fixed

Charles Keche

• Feb 1st, 2018

 

Severity always applies to business impact while Priority is the impact to test progression..so the business e.g. BA or Product owner will determine the severity while the test assigns the priority according to how many test scripts are being affected or blocked.