In my view there will not be that kind of situation since 
the whole purpose of testing is to avoid the bugs that are 
affecting the system. therefore, priority will be definitly 
high when severity is high.

load conditions(severity- high)
ex: does not allows load(proirity-high)
ex:does not allow customer expected load(proirity-low)

When you get serious bug or critical bug, but its very rare 
snerio to get this bug then this bug have high sevrity and 
low priority.

Hi,

    Ex: u opened naukri.com and u searching for testing 
opps are there or not.. while searching u are entering 
domain name , exp ..suppose if "exp"  functon is not 
working also u can retrieve the results by using Domain name
Here functionality is not working but u can another way is 
there to retrieve the details.the client can not bother abt 
the Exp function.. then we can give the sevirity as High 
and Priority sa Low...

Let me know if it is wrong.


Regards,
Satya.k

If u have to test any link or screen related to the 
functionality that u r currently working,but that link or 
screen is of out of scope,then u can give high severity n 
low priority for that.