How would you prioritize your bug?

 Bugs that affect core functionality or negatively affect users should be given the highest priority. Bugs that are affecting a small number of users but are causing significant problems should also be given high priority.

 

1. Critical - Critical bugs are those that can cause serious problems if not fixed. They should be fixed as soon as possible.

2. High - High-priority bugs are those that may cause some inconvenience, but don't necessarily pose a threat to the system or users. They should be fixed as soon as possible, but may not take priority over critical bugs.

3. Normal - Normal-priority bugs are those that don't necessarily affect the system or users, but could still be fixed if necessary. They should not be ignored, but may not take priority over other bug fixes.

4. Low - Low-priority bugs are those that do not pose a threat to the system or users, but could still be troublesome if not fixed. They should only be addressed if there is no other option and they don't conflict with other projects.

Comments

Post a Comment

Popular posts from this blog

What happens in requirement analysis phase in SDLC?

Image
For any  software development life cycle  (SDLC), the requirement phase is the first step toward unambiguity. It is an essential step because it reverberates with acceptance tests which are crucial for the end user acceptance. Here is the complete process of the requirement analysis and gathering phase of SDLC – Requirement gathering Also known as elicitation, software development requirements gathering is followed by an analysis of the needs so that the technology experts shall go for feasibility tests and may alter some objectives to convert the thoughts into a real product. The gathering technique involves precise research on what customers need. Nevertheless, it is not possible to put a survey questionnaire to each customer and get feedback; hence, the requirement for product, tool, or objectives is asked to the stakeholders who influence the product or who are well acquainted with the end users. The stakeholders could be software quality engineers or at times even...
Read more

What are the drawbacks in waterfall software development mode?

  What is the Waterfall Method? The Waterfall Model is a linear or sequential approach to project management and works based on fixed dates, requirements, and outcomes. Teams do not require consistent communication and, unless specific integrations are required, can be self-contained. Team members can also work independently and are often required to provide status reports somewhat less frequently (when compared to an agile approach). A typical Waterfall project is chronological and is made up of the following phases: Requirements Design Implementation Verification Maintenance Disadvantages of the Waterfall Model 1 . The waterfall model doesn’t support making changes. 2. It can invalidate the work you’ve previously accomplished. 3. This method excludes end-users and clients. 4. It delays testing until after the completion of the project. 5. The waterfall model can promote longer delivery times. 6. It typically works better for small projects. 7. Working m...
Read more