Suppose in one banking application there is one module ATM 
Facility. in that ATM facility when ever we are 
dipositing/withdrawing money it is not showing any 
conformation message but actually at the back end it is 
happening properly with out any mistake means only missing 
of message . in this case as it is happenig properly so 
there is nothing wrong with the application but as end user 
is not getting any conformation message so he/she will be 
confuse for this.

So we can consider this issue as HIGH Priority but LOW 
Severity defects..

If it not clear please write to me..
panibiswajit@yahoo.com

U will get these type of issues in UAT.

In UAT, though the severity is very low the priority should 
be high.

If there is a spelling mistakes in Front page i.e login 
page of the application then that comes under High priority 
and low severity.

For example if SATYAM is printed as SAYAM in front page, 
since it draws the customers attention thes this cosmetic 
bug should be fixed immediately as it is a question of 
company prestiage.

So all cosmetic errors that or in Front page of the 
application only comes under High priority and Low severity
(since it is not relating to any functionality).

If iam wrong pls let me know

can any one give example of High severity and low priority 
bug?

Suppose in application SAVE button is there and u have
clicked it 200 times. After that it is getting crashed.In
this situa tion status will be high Severity & Low priority.

The best answer is ...

Suppose you have acquired yahoo company and you want to 
change the name of yahoo then the word should be eliminated 
from all over the YAHOO site. If it is present then the 
priority should be high and severity is low since the word 
should not have any impact on the functionality but that 
should not be present.