HIGH SEVERITY with LOW PRIORITY bug desciption Go thru the following description,

If u need to display INSURANCE calculations lets say Employee Insurance Info Report In that REPORT u have to display all employees insurance calculations based on their benfits assigned for the financial year 2010. And management told you that u should display all correct calculation in the report before next month . now you got bug in REPORTS that shows wrong calculations and display insurance based on year 2009 i.e. last year.(Expected : It should display calculations based on 2010 employee benefits) NOW, in this case u can describe this bug as a Hight serverity bug because this would affect on insurance calculations at the time of delevery and Financial Audit but now, You give LOW PRORITY to resolve this issue (depends on your work status also :) ) because this bug occurs in REPORTS only not in your applications pages from where you provides inputs for new calculations and all these pages shows correct insurance calculations. so bug is in only reports and as per managemnet told you to show correct reports before the next months. i.e. you have more than one month in hand to resolve the issuee. ( and prior to resolve this you have to schedule time for resolve high priorty issues also ) So in this case you can give Low Prioriy for this high severity bug :)

so in this scenario there is chances to give HIGH SEVERITY with LOW PRIORITY bug desciption Re: Example of Severity and Priority Priority :- How quickly we need to fix the bug? Or How soon the bug should get fixed? Severity : - How much the bug is effecting the functionality of the application? Eg:(1) High Priority and Low Severity If a company logo is not properly displayed on their website. (2) High Priority and High Severity Suppose you are doing online shopping and filled payment informations, but after submitting the form, you get a message like "Order has been cancelled." (3) Low Priority and High Severity If we have a typical scenario in which the application get crashed, but that scenario exists rarely. (4) Low Priority and Low Severity There is a mistake like "You have registered success" instead of successfully, success is written.

Re: Example of Severity and Priority Hi, Severity: Describes the bug in terms of functionality. Priority: Describes the bug in terms of customer.

few examples: High Severity and Low Priority -> Application doesn't allow customer expected configuration. High Severity and High Priority -> Application doesn't allow multiple user's. Low Severity and High Priority -> No error message to prevent wrong operation. Low Severity and low Priority -> Error message is having complex meaning. Defect Severity determines the defect's effect on the application where as Defect Priority determines the defect urgency of repair. Severity is given by Testers and Priority by Developers 1. High Severity & Low Priority : For example an application which generates some banking related reports weekly, monthly, quarterly & yearly by doing some calculations. If there is a fault while calculating yearly report. This is a high severity fault but low priority because this fault can be fixed in the next release as a change request. 2. High Severity & High Priority : In the above example if there is a fault while calculating weekly report. This is a high severity and high priority fault because this fault will block the functionality of the application immediately within a week. It should be fixed urgently. 3. Low Severity & High Priority : If there is a spelling mistake or content issue on the homepage of a website which has daily hits of lakhs. In this case, though this fault is not affecting the website or other functionalities but considering the status and popularity of the website in the competitive market it is a high priority fault.

4. Low Severity & Low Priority : If there is a spelling mistake on the pages which has very less hits throughout the month on any website. This fault can be considered as low severity and low priority.