Thread: Which is given first preference priority or seviority

Originally Posted by supraja.ivatury

When we come across a bug, it is given both priority and seviority. Now on what basis bug is cleared? Which is given first preference priority or seviority? In my view seviority is given first prefarence.

See priority decides on the basis of severity and time schedule.So, by default more stress goes to severity, but if it has been assigned any priority then that will followed.

Hi,

Look into "Geeks Talk > Software Testing > Testing Issues> difference between severity and priority" asked by sunny_love on 6/1/2006. You can easily understand and get the right answer from that discussion.

Hello aardvax and smartarun ,

First read the question carefully...

When we come across a bug, it is given both priority and seviority. Now on what basis bug is cleared? Which is given first preference priority or seviority? In my view seviority is given first prefarence.

Now give to the point answers, ok.

Tester assigned the severity of the bug.Now tester works completed.Now it's the task of CCB to assign priority.And bug will fix according to that.So, who got the preference (as the question is?) for fixing bugs, of course priority.

One more thing to disclose is that severity once assigned never change, but priority can change during bug fixing process.I hope now it should clear to all and it is more than sufficient discussion on this question.

Originally Posted by jainbrijesh

Hello aardvax and smartarun ,

First read the question carefully...

When we come across a bug, it is given both priority and seviority. Now on what basis bug is cleared? Which is given first preference priority or seviority? In my view seviority is given first prefarence.

Now give to the point answers, ok.

Tester assigned the severity of the bug.Now tester works completed.Now it's the task of CCB to assign priority.And bug will fix according to that.So, who got the preference (as the question is?) for fixing bugs, of course priority.

One more thing to disclose is that severity once assigned never change, but priority can change during bug fixing process.I hope now it should clear to all and it is more than sufficient discussion on this question.

Hi Jain
I really praise you for your explanation of the question which was asked...
and obviously it is the job of the developers to seek for the preference of fixing the bug according to the priority given..but we do not go ahead in development of a quality product if testers and developers are at logger heads...i just tried that a conformance is necessary in interpretaion of the terms used in every organisation...and priorities are assigned based on severiites...offcourse when priorities have been decided such that testers can tolerate the delay or whtsoever in case of a raised and opened bug...then prority is the first preference to fix the bug....like a straight mathematical question.....
thanks for your post

and you know the best thing
we alll are saying the same thing

Originally Posted by varmakub

I happend to hear that my friend who is working in one of MNC to whom they don't have seviority while logging the bug (means the option is disabled in QC). So it would be based on the company and the process which they follow.

Do I know the name of that MNC?

Because as I know severity column can never left blank in bug reporting.It's very important as later decisions depend on it.

Well, I am not too accustomed to bug reporting, but I tend to agree with jainbrijesh. Severity column is most important. I also know that the bugs are prioritized based on the severity level of the bug.

It is obvious that a bug with high severity will have high priority. So, at the end of it all it doesn't really matter. If a bug has high priority, it also means that it rather severe(Except for timeline based bugs like, if the bug is not rectified within a period of time, then it might have severe business impacts though it is of less severity now).

So, at the end of the day, bugs are fixed on priority basis. And how the prioritites are fixed? Based on severity -in most of the cases.

So, aardvax is right. We are all telling the same thing
Hope this helped settling the issue.

Cheers!
Kalayama

Originally Posted by varmakub

I totally disagree My Friend !!!
QC Administrator has all the rights to disable few columns as well as setting mandatory fields to the existing columns in QC. So in this case Severity can be left blank if it’s not a mandatory :-) as set by the QC Admin

Hello varmakub,

I am not saying that it can't be done.
What I am saying is that it's not looking right logically.
If we don't have the severity, It means all bugs will be fixed and all bugs are equal severe, which is not possible in real scenario.

That's it.Otherwise, nothing is impossible, because impossible itself says "I M Possible".

hi

Reffer to this link http://www.geekinterview.com/talk/15...light=proirity
posted in software testing then u will get more details of Proirity and severity while looking into this link

Severity:- The impact of bug in term of application or how crtically it is, will effect the whole system. This severity is given by testers and once the severity is assigned for bug it never change. It is clasified into 4 types
1. Crtical ( not able to continue test execution ex: file not found, requested URL could not be retrieved)- Showstopper
2. High ( not able to continue test execution with out resoloving that defect)- Input domain bugs, output come bugs, H/W bugs, Control flow bugs etc....
3. Medium ( able to continue test execution but manditory to resolve) - Error handlling bugs, Virsion control bugs, source bugs etc...
4. Low ( able to continue test execution but may or maynot to resolve) - User interface bugs, id control bugs etc....

Priority:- The impact of bug in terms of client requirements or how quickly we need to be fix bug. This priority is given by TL/PL/CCB/QC and changes may be occur during bug fixing depends upon the time schedule and severity of bug.
It is classifeed into 3 types
1. High ( most urgency to fix it)
2. Medium (no urgent but to fix that defect so early)
3. Low (less uregency to fix that defect)

Bug fixing depends upon priority, priority depends upon the severity and time schedule, severity depends upon the functionality of application

examples for
1. high priority and low severity - Spelling mistakes in a screen, , wrong logo, logo missing etc..
2. low priority and high severity - Taking invalid input, final out put is wrong, device is responding wrongly, etc...
3. high priority and high severity - does not take valid type, dependent outputs are wrong, system deadlocks, etc
4. Low severity and low proirity - improper alignments

varmakub and bharathi_ark, no one of you have posted the to the point answer.

vikas_goel28 has asked for example and you are explaining the definitions of severity and priority.


So, please post according to question.

1. high priority and low severity (Company logo is not clearly visible)
2. low priority and high severity (Broken link)
3. high priority and high severity (Database connectivity bugs)

In addition to them...

4. low priority and low severity (User interface bug)

Yes, a tester can decide both severity and priority,it depends on company working process.Even in some company there is combined term for (severity+priority).

"if company logo is not clearly visible and we can not access inbox then which bug need to be resole first?"

Both will have equal priority, now it depends on developer, to which he fix first.