Changes between Version 6 and Version 7 of HowToRankTicket
- Timestamp:
- Oct 6, 2016, 5:19:22 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
HowToRankTicket
v6 v7 10 10 ''' 2) Severity:''' 11 11 12 It is the extent to which the defect can affect the software. In other words it defines the impact that a given defect has on the system. For example: If an application or web page crashes when a remote link is clicked, in this case clicking the remote link by an user is rare but the impact of application crashing is severe. So the severity is high but priority is low.12 It is the extent to which the defect can affect the software. In other words it defines the impact that a given defect has on the system. '''For example''': ''If an application or web page crashes when a remote link is clicked, in this case clicking the remote link by an user is rare but the impact of application crashing is severe. So the severity is high but priority is low.'' 13 13 14 14 Severity can be of following types: … … 23 23 '''3) Priority:''' 24 24 25 Priority defines the order in which we should resolve a defect. Should we fix it now, or can it wait? This priority status is set by the tester to the developer mentioning the time frame to fix the defect. If high priority is mentioned then the developer has to fix it at the earliest. The priority status is set based on the customer requirements. For example: If the company name is misspelled in the home page of the website, then the priority is high and severity is low to fix it.25 Priority defines the order in which we should resolve a defect. Should we fix it now, or can it wait? This priority status is set by the tester to the developer mentioning the time frame to fix the defect. If high priority is mentioned then the developer has to fix it at the earliest. The priority status is set based on the customer requirements. '''For example''': ''If the company name is misspelled in the home page of the website, then the priority is high and severity is low to fix it.'' 26 26 27 27 Priority can be of following types: … … 35 35 '''Few very important scenarios related to the severity and priority''' 36 36 37 High Priority & High Severity: An error which occurs on the basic functionality of the application and will not allow the user to use the system. (Eg. A site maintaining the student details, on saving record if it, doesn’t allow to save the record then this is high priority and high severity bug.)37 '''High Priority & High Severity''': An error which occurs on the basic functionality of the application and will not allow the user to use the system. (Eg. A site maintaining the student details, on saving record if it, doesn’t allow to save the record then this is high priority and high severity bug.) 38 38 39 High Priority & Low Severity: The spelling mistakes that happens on the cover page or heading or title of an application.39 '''High Priority & Low Severity''': The spelling mistakes that happens on the cover page or heading or title of an application. 40 40 41 High Severity & Low Priority: An error which occurs on the functionality of the application (for which there is no workaround) and will not allow the user to use the system but on click of link which is rarely used by the end user.41 '''High Severity & Low Priority''': An error which occurs on the functionality of the application (for which there is no workaround) and will not allow the user to use the system but on click of link which is rarely used by the end user. 42 42 43 Low Priority and Low Severity: Any cosmetic or spelling issues which is within a paragraph or in the report (Not on cover page, heading, title).43 '''Low Priority and Low Severity''': Any cosmetic or spelling issues which is within a paragraph or in the report (Not on cover page, heading, title).
