Priority - Priority is the order in which developer has to fix the bug.
Severity - Severity is how seroisly the bug is impacting the application.
Eg.
High Priority & High Severity:
1. A show stopper error which occurs on the basic funcationality of the application . (Eg. A site maintaing the student details, on saving record if it, doesn't allow to save the record then this is high priority and high severity bug.)
2. The application crashes whenever a person attempts to submit valid input on the registration page.
3. Suppose you are doing online shopping and filled payment informations, but after submitting the form, you get a message like "Order has been cancelled."
High Priority & Low Severity:
1. The spell mistakes that happens on the cover page or headin or title of an application.
2. The content entered in the Terms of Use are not correct and could potentially lead to legal consequences.
Low Severity -High priority:
1. spelled there as 'Gaogle'.Though, it doesnt affect the basic functionality of the software,it needs to be corrected before the release. Hence, the priority is high.
High Severity & Low Priority:
1. The application generates a show stopper or system error, (for which there is no workaround) but on click of link which is rarely used by the end user.
2. The application crashes whenever a person enters 1500+ chars in a phone number text box that should accept no more than 15 chars.
Low Priority and Low Severity:
1. Any cosmetic or spell issues which is with in a paragraph or in the report (Not on cover page, heading, title).
2. There is a slight misspelling on one of the FAQ pages.
Low Priority and High Severity:
1. If we have a typical scenario in which the application get crashed, but that scenario exists rarely.
2. There is a mistake like "You have registered success" instead of successfully, success is written.
