Preetha

• Nov 21st, 2006

 

Severity:How severe/serious the issue is.

Priority:How important the issue is.

High severity,High Priority:Very serious,very important....Get it done ASAP.

High Severity,Low Priority:Very serious,not very important....Get it done while you can before the deadline.

Low Severity, Low Priority:Not serious,not important.....Get it done leisurely but before the deadline.

Low Severity, High Priority:Not serious,but very important.Get it done ASAP.

RAMANA

• Nov 22nd, 2006

 

Sevearity: severearity is related to the software program part i.e how sevear the bug effecting our software developed by our company.

Priority : priority related to the client side.i.e How important to client to solve that particular bug.

Example : Take a login box(imagine as yahoo login id).

Client requirement is not to enter alphabets

while we testing if we find,if we enter alphabets its allowing alphabets means we should consider that bug as High Priority.

while we testing if we find , if we enter special characters the system crashes means it will be High Sevearity ,but not High priority means Low priority why because client does not have any requirement for that.

Finally, i want to say High sevearity bugs may not having High Priority.

srinivas.o

• Dec 11th, 2006

 

Hi,

severity: Severity is nothingbut seriousness of defect wrt build.All funtionality bugs,database bugs and performance bugs are under high  severity...

Cosmotic bugs are under low severity..In between that under Medium Severity....

Priority: Priority depends on importance of bug wrt client/customer..