In the Bug Tracking the terms “Priority” and “Severity” are used to share the importance of a bug among the team and to fix it accordingly. Priority means how fast it has to be fixed. Normally talking about this, “High Severity” bug are marked as “High Priority” bugs & it’s should be resolved as early as possible, but this case is not all the time. There can be different exceptions to this rule and depending on the nature of the application it can be change from company to company. Let’s take a example to the Priority: e.g. To deal with all issues present what issues to be consider on first based on its urgency or importance on application under test. Priority: Priority means how fast it has to be fixed. Priority is related to scheduling to resolve the problem. Severity means how severe it is affecting the functionality. Is largely related to Business or Marketing aspect. It is a pointer towards the importance of the bug. The priority status is set based on the customer requirements. Is related to technical aspect of the product. It reflects on how bad the bug is for the system. Priority means how urgently the issue can be fixed. Product manager is to decide the Priority to fix a bug. Based on ‘Project Priorities the product fixes are done. The Priority status is set by the tester to the developer mentioning the time frame to fix a defect. If High priority is mentioned then the developer has to fix it at the earliest. Severity: It is totally related to the quality standard or devotion to standard. Severity means how severe it is affecting the functionality. Severity is associated with standards. The severity type is defined by the tester based on the written test cases and functionality. Is related to technical aspect of the product. It reflects on how bad the bug is for the system. It is totally related to the quality standard or devotion to standard. Severity means how big functionality is affecting of the product. The Test Engineer can decide the severity level of the bug. Based on Bug Severity the product fixes are done. Also we can say The Severity status is used to explain how badly the deviation is affecting the build. The severity is assigned by tester. Based on seriousness of the bug severity is assigned to defect. It can be divided into four categories: Show Stopper: 4 – Cannot able to test application further. Major Defect: 3 – Major functionality not working but able to test application. Minor Defect: 2 –Bug in Functionality but in the sub module or one under the other module. Cosmetic: 1 – Issues in location of the object or the look and feel issue.