zulfi

• Jul 26th, 2005

 

Priority tells U how Important the bug is. 
Severity tells U how bad the bug is. 
Severity is constant....whereas priority might change according to schedule. 

SatishTKakade@yahoo.com

• Jul 26th, 2005

 

Priority means how urgently bug is needed to fix  
Severity means how badly it harms the system

Venkat ramana

• Jul 27th, 2005

 

priority defines how fast the bug should be resolved , where as the severity defines how severe the bug it is.It can be known by the extent of negative impact on the related and other functionalities

subha

• Sep 5th, 2005

 

based on severity priority is given.in other words if the bug is severe to a greater extent then the bug is given the higher priority.if it fatal then it is assigned a lower priority. 
 
example for high seviority is :the data entered for employee sonali are entered in to some others personals for example sudha.that means the personal details of sonali were lost and that of sudha's were changed.in this case it is more severe.

subha_11_2004@yahoo.co.in

• Sep 6th, 2005

 

Posted by subha on 2005-09-05 21:27:39 
based on severity priority is given.in other words if the bug is severe to a greater extent then the bug is given the higher priority.if it fatal then it is assigned a lower priority.  
 
example for high seviority is :the data entered for employee sonali are entered in to some others personals for example sudha.that means the personal details of sonali were lost and that of sudha's were changed.in this case it is more severe.  

subha

• Sep 11th, 2005

 

see we cannot say in a single sentence about prioritising a bug .there r no of reasons for this.u can read the given below and understand.Priority is Business; Severity is Technical In Triages, team will give the Priority of the fix based on the business perspective. They will check “How important is it to the business that we fix the bug?” In most of the times high Severity bug is becomes high Priority bug, but it is not always. There are some cases where high Severity bugs will be low Priority and low Severity bugs will be high Priority. if schedule drawn closer to the release, even if the bug severity is more based on technical perspective, the Priority is given as low because the functionality mentioned in the bug is not critical to business. Priority and Severity gives the excellent metrics to identify overall health of the Project. Severity is customer-focused while priority is business-focused. Assigning Severity for a bug is straightforward. Using some general guidelines about the project, testers will assign Severity but while assigning a priority is much more juggling act. Severity of the bug is one of the factors for assigning priority for a bug. Other considerations are might be how much time left for schedule, possibly ‘who is available for fix’, how important is it to the business to fix the bug, what is the impact of the bug, what are the probability of occurrence and degree of side effects are to be considered. Read the excellent article Arguing Apples and Oranges This article clearly explains the how Priority and Severity of the bug given. Some of the above points taken from this article Many organizations mandate that bugs of certain severity should be at least certain priority. Example: Crashes must be P1; Data loss must be P1, etc. A severe bug that crashes the system only once and not always reproducible will not be P1, where as an error condition that results re-entry a portion of input for every user will be P1 Microsoft uses a four-point scale to describe severity of bugs and three-point scale for Priority of the bug. They are as follows Severity ---------------1. Bug causes system crash or data loss.2. Bug causes major functionality or other severe problems; product crashes in obscure cases.3. Bug causes minor functionality problems, may affect "fit anf finish".4. Bug contains typos, unclear wording or error messages in low visibility fields. Priority---------------1. Must fix as soon as possible. Bug is blocking further progress in this area.2. Should fix soon, before product release.3. Fix if time; somewhat trivial. May be postponed.

Shaik

• Sep 24th, 2005

 

Hi

Prority   : Urgency Of the Bug

Severity : Impact of the Bug 

Vishal Vaidya

• Feb 15th, 2006

 

I do notagree with the statement that "Higher the severity, more will be the priroty" Its very much possible that the bug is highly severe but has got very low priority.

vandanasagar2006

 Profile Answers by vandanasagar2006 

• May 10th, 2006

 

BUG SEVERITY: is the extent to which the presence of a bug in s/w has affected the performance , usability, posing various problems for workaround and other bisiness decisions is called BUG IMPACT or BUG SEVERITY.BUG PRIORITY: Describes the importance and order in which the bug should be fixed."Severity is fixed.......... whereas priority might change according to schedule.

SwapnaPavan

• Sep 15th, 2006

 

Priority: Order to fix the bug

Severity: Complexity/criticality of the bug

jainbrijesh

 Profile Answers by jainbrijesh Questions by jainbrijesh

• Jan 2nd, 2007

 

severity tells about how bad the bug is?whereas Priority tells how quickly the bug should be fixed.

swaraj

• May 31st, 2007

 

Priority :

Priority defines which bug we need to fix asap. Priority always define by the importance of the functionality. If the functionality cause more impact on the application or customer then priority should High of that bug.

severity :

severity means how much it impacts on the project/application.

Chary

• Aug 11th, 2007

 

Severity is given by the Test Engineer how serious is bug
Poiority is given by Developers depend upon the severity. in some cases depends upon requirement.

savitha vaidya

• Oct 15th, 2007

 

Yes. There could be low severity - high priority bugs.

mithr17

 Profile Answers by mithr17 

• Nov 30th, 2011

 

I agree with everyone who said priority is based on business and severity is based on the technical severity.

That is how the bugs are triaged!