Bug Prioritization - What are the 5 levels of priority?
Last updated: March 01, 2024 Read in fullscreen view
- 17 Jul 2023
What Is SSL? A Simple Explanation Even a 10-Year-Old Can Understand 43/121 - 05 Jul 2020
What is Sustaining Software Engineering? 39/1302 - 18 Oct 2020
How to use the "Knowns" and "Unknowns" technique to manage assumptions 38/1089 - 01 Mar 2023
What is Unit Testing? Pros and cons of Unit Testing? 29/439 - 01 Oct 2020
Fail fast, learn faster with Agile methodology 24/1047 - 14 Oct 2021
Advantages and Disadvantages of Time and Material Contract (T&M) 22/864 - 20 Mar 2022
What is a Multi-Model Database? Pros and Cons? 21/1164 - 18 Aug 2022
What are the consequences of poor requirements with software development projects? 20/274 - 13 Dec 2020
Move fast, fail fast, fail-safe 20/323 - 06 Feb 2021
Why fail fast and learn fast? 20/451 - 10 Dec 2021
What is a Kano Analysis? 19/889 - 03 Jul 2022
What is the difference between Project Proposal and Software Requirements Specification (SRS) in software engineering? 17/1025 - 23 Sep 2021
INFOGRAPHIC: Top 9 Software Outsourcing Mistakes 17/439 - 10 Nov 2022
Poor Code Indicators and How to Improve Your Code? 16/231 - 31 Dec 2021
What is a Data Pipeline? 16/215 - 10 Apr 2022
What is predictive analytics? Why it matters? 15/192 - 19 Oct 2021
Is gold plating good or bad in project management? 15/816 - 25 Apr 2021
What is outstaffing? 14/270 - 19 Apr 2021
7 Most Common Time-Wasters For Software Development 14/556 - 22 Sep 2022
Why is it important to have a “single point of contact (SPoC)” on an IT project? 14/940 - 30 Jan 2022
What Does a Sustaining Engineer Do? 14/617 - 13 Nov 2021
What Is Bleeding Edge Technology? Are bleeding edge technologies cheaper? 13/539 - 08 Oct 2022
KPI - The New Leadership 12/603 - 31 Oct 2021
Tips to Fail Fast With Outsourcing 12/392 - 10 Dec 2023
Pain points of User Acceptance Testing (UAT) 11/452 - 07 Dec 2023
The Myths Of Requirements 10/256 - 05 Jan 2024
Easy ASANA tips & tricks for you and your team 10/201 - 11 Jan 2024
What are the Benefits and Limitations of Augmented Intelligence? 10/478 - 17 Feb 2022
Prioritizing Software Requirements with Kano Analysis 10/304 - 28 Dec 2021
8 types of pricing models in software development outsourcing 10/437 - 10 Nov 2021
Automated QA Outsourcing – Hire a Professional Software Testing Team 9/557 - 12 Mar 2024
How do you create FOMO in software prospects? 9/167 - 14 Mar 2024
Why should you opt for software localization from a professional agency? 6/140 - 26 Dec 2023
Improving Meeting Effectiveness Through the Six Thinking Hats 6/254 - 06 Nov 2019
How to Access Software Project Size? 6/249 - 02 Apr 2022
Productivity vs. Efficiency – What Are the Differences? 5/213
Prioritizing bugs based on their impact on the user experience will allow you to deliver a product that meets or exceeds customer expectations. By addressing high-priority bugs that directly affect critical functionality or cause significant inconveniences, you can improve overall user satisfaction and loyalty.
Standard priority rules
Each bug is assigned the first appropriate priority listed below from top to bottom.
P1 - Critical
- Any reproducible crash or hang.
- Any regression from a previous publicly released version.
- Serious problems on important sites due to site change or newly-important sites.
- Serious security issue.
- The deadline can be either ASAP, same-day, or next-day turnaround
P2 - High priority
These bugs are very important and must be completed ASAP. Because these bugs are not time-sensitive, this type of bug comes second on the priority scale after critical bugs.
Bugs are high-priority when:
- Site that does not function in some non-trivial way.
- Serious performance complaints.
- Site that has really bad cosmetic problems (e.g., content overlapping such that it’s very hard to read).
- Unreproducible crash or hang that has been reported many times.
- Deadline can be within a couple of days or end of the week.
P3 - Medium
- Site that works but has some cosmetic problems.
- Minor performance complaints, such as trivial memory leaks
- rchitecture issues that could help with correctness or performance but are not a clear win in advance.
- Unreproducible crash or hang.
- Deadlines are outlined.
P4 - Low priority
All enhancement requests and feature requests did not cover the criteria for P1, P2, or P3.
P5 - Unknown
P5 is not used for bugs. At TIGO, we shares its Bugzilla or Redmine with other projects who might use it, that’s why it’s still there.
Common adjustments to priority
- If there is a workaround, the priority may be moved down.
- If a bug gets a lot of duplicates, the priority may be moved up.
- If a bug is getting a lot of public attention, the priority may be moved up.
- If a bug is on a very important site, the priority may be moved up.










Link copied!
Recently Updated News