Yes it is possible

a defect with high severity and low priority

and

with Low severity and high Priority.........

as Severity and Priority both are different concepts......

Regards

Biswajit Pani ( 09986183456 )

panibiswajit@yahoo.com

Hello friends

ya its possible for this i will give a example with scenario.

when the developmenpment team prepared the modules and they sent it for testing and after doing some part of testing then a bug raised in the first module its seviority is minor and at the same time in second module a bug raised and its seviority is major. we came to know the by the next day the client is comming for inspection and he wanted to get the first module prepared. so at this time less seviority bug gets high priority and high seviority bug gets less priority.

i think u can understand wht i want to say.

if any thing wrong in this pls inform me.

regards

aravind

Hello

Your scenario is valid when there is a client and a company(where the product is developed and released to the client).In a scenario like client and company both are same i mean if a company wants to develop a product and wants to use for their own use than how can we set the priority low and severity high or vice versa ?(There are some big organizations in the market where they are having inbuilt software unit to develop their own products).

--Raghu

Bascically ther are two types of defects ...1)low severity defect and 2)high priority defect.....

high severity defect is usally said to be occured when the defct occurs to the basic priority objects where as low severity defect is usalyy said when the defect is said to be the supportive to the basic priority......

I have a formula for priority i.e Priority Severity (Vs) Ratings

Rating is the rate of occurence--Usually occures Sometimes occurs Never Occur

Severity is the seriousness or impact of that defect over the functionality----Critical High Medium Low

Priority refers to the order (High Medium Low) in which defects need to be fixed by developer.

Example :

Priority Critical (Vs) Usually occures High

Medium Vs) Sometimes Medium

This is absolutely a controversial statement my dear friend. I was amazed how could you compare Severity and priority into requirements or specification? If I am wrong can you please tell me in detail how you are relating this scenario. selvamohan@gmail.com (+919886732478)

Priority and Severity are two different entities but when it comes in correlating for setting the status of a bug they both come together into picture. For instance let us take a scenario that you are testing a web page with login form with username and password field. You observe that when you type password its like ordinary text field displaying characters not in * format. Won't you rise that defect as High Priority and High Severity . Yes i do agree that you also can have scenarios like making a High Severity and Low priority bug but not all the time since both the entities are related mostly. Do keep this in mind when you are posting any defect.

Regards

Selvamohan Chinnasamy (+919886732478) mohi_v@yahoo.co.in for Yahoo IM cselvamohan for Skype

Hi

There are lot of comments for this question. In one of your comments you said that there is a controversial statement. But i am not able to understand to which comment are you pointing in the list of comments?

--Raghu

Let us take an example .

Take a project like some thing rediff(name of application).We all know the main window name must be the project name and we can see on title bar.

If there is spelling mistake in name say redif then this comes under high priority and low severity because application name must be right.

For calculations we can say high priority and high severity.