Defect Triage Process in Software Testing | Complete Guide

In this article, we bring complete details on What is Defect Triage (Bug Triage), Defect Triage Meeting Process, and How to handle Defect Triage Meetings.

Defect Triage Bug Triage

What is Defect Triage?

Defect Triage is also known as Bug Triage.

Don’t get confused with the terms Bug and Defect. You check the difference between Defect, Bug, Error & Failure here.

Also, you can check the Defect Life Cycle and How To Write A Good Bug Report.

The term Triage is used in Software Testing to define the severity and priority of defects. Defect triage is a process or mechanism where each defect is prioritized based on its severity, risk, reoccurrence, etc.,

Triage is a medical word. Triage is the process of quickly examining patients who are taken to a hospital in order to decide which ones are the most seriously ill and must be treated first. Patients will be categorized based on the severity of the illness and then the doctors treat the patients who are seriously ill on a priority basis. Patients who have non-critical diseases are considered as low priority patients and were treated after the patients who are seriously ill.

In Software Testing, we use the word Triage with the combination of Bug/Defect like Bug Triage or Defect Triage. Here we apply the same concept to bugs found during the testing phase. It is to decide the priority of the bugs based on their severity, risk, and frequency of reoccurrence, etc.,

Defect Priority Vs Defect Severity

What is Defect Triage Meeting?

Bug Triage Meeting

Bug Triage Meeting is done to sort out the priority of all open bugs. When and how these open bugs need to be fixed is decided in this Defect Triage Meeting.

The objective of a triage meeting is to track all the defects and makes sure the correct resolution in a timely manner.

During Defect Triage Meetings, Triage Teams decide how to categorize and prioritize defects. Categories often used are

  1. We are going to fix this now
  2. We are going to fix this later
  3. We are never going to fix this

Defect Triage comes into the picture in Software Testing when there are no sufficient resources to handle the defects. Imagine a situation where there are a number of defects are more and the resources to handle those are limited. In this case, defect triage helps to get as many defects resolved as possible by assessing the defects and prioritize them based on the severity of the defects.

The frequency of the Software Bug Triage meeting is weekly, monthly, on each sprint (defect triage in Agile). It varies from project to project.

What is the process of the Defect Triage Meeting?

The defect triage process is as follows:

  1. Defect Review
  2. Defect Assessment
  3. Defect Assignment

The triage team reviews the defects to fix the defects. Defect assessment will be done on the basis of defect severity. In this assessment process, the triage team will decide whether these defects are needed to be fixed or kept on hold, or removed from the list. The defects which are in the list of ‘to be fixed’ will be assigned to the concerned department/person after proper analysis of the defects.

What are the questions raised during the Defect Triage Meeting?

Questions raised during the Defect Triage Meeting are as follows:

  1. Is this bug valid?
  2. What is the severity of the bug?
  3. When to fix this bug?

These questions will be applied to each and every defect in the list of all open bugs.

What is the purpose of having a Defect Triage Meeting?

The purpose of defect triage meeting in the Software Development Process is to prioritize the defects based on their severity, risk, reoccurrence, etc., Team involved in Defect Triage Meeting should have a proper defect triage meeting agenda and validate severities of the defect, make changes as required, finalize resolution of the defects, and assign resources to fix it.

Who are the participants in the Defect Triage Meeting?

Test Lead, Development Lead, and Project Manager are the main participants in the Defect Triage Meeting as these people will discuss all the defects and take necessary action. It’s more like having one person from each department. The test lead is the one who has knowledge of the bug which was recorded. The development lead is the one who can give an idea on how to fix the bug and also can explain technical hurdles if any. The Project Manager is the one who has a better understanding of whether or not the bug is actually a bug or if it’s a feature request.

Participants in the Defect Triage Meeting are as follows:

  1. Test Lead
  2. Development Team Lead
  3. Project Manager
  4. Test Manager
  5. Product Manager
  6. Testers
  7. Developers
  8. Business Analyst

There is no rule like everyone should involve in this meeting. It varies from company to company. Mandatory participants are Project Manager, Test Lead, and Development Lead. Test Lead or Project Manager invites other members whenever necessary to get feedback regarding specific bugs. This entire team is known as Triage Team.

What are the Roles and Responsibilities of the Triage Team during the Defect Triage Meeting?

1. Test Lead:

  • Test Lead schedules a defect triage meeting and sends out a formal meeting invite along with the defect report to the Triage Team
  • Assigns priority and severity of the defects
  • Gives presentation on each defect so that each triage team member understand the root cause of defects
  • Makes a minutes of meeting and shares with the Triage Team after the meeting

2. Project Manager:

  • Involves in assisting the team in the process of prioritizing the defects
  • Involves in tracking the issues list
  • Involves in gathering the confirmation from Dev Team for the next release date for QA
  • Ensures that whether all the participants from every team is available for the meeting
  • Acts as a mediator and takes necessary decisions, if any dispute or conflict occurs between the teams

3. Development Team Lead:

  • Helps in the process of prioritizing the defects
  • Explains the defect complexity and risk involved in fixing the defect to the participants
  • Allocate work to appropriate developers to get the defects fixed

What are the activities carried out in the Defect Triage meeting?

I have worked on an ERP project. The size of the product is huge and the frequency of reporting bugs is high. Due to the high volume, our Project Manager used to call for a Defect Triage meeting every two weeks once.

Once the Project Manager or Test Lead decides to setup a Triage Meeting then Test Lead invites Triage Team to the meeting. Test Lead conveys a bug report with the new defects presented since the last gathering. The reason behind sharing bug reports is to get an idea of each bug before joining the meeting.

The activities carried out in the bug triage meeting are as follows:


All the participants should understand the bugs, so testers should take responsibility in the following points

  1. To provide enough information in the bug description
  2. Posting the bugs under an appropriate category
  3. To verify the severity and priority which was assigned to each bug

During the meeting:

  1. Once the meeting kickstarts, participants in the meeting discuss the previous triage meeting’s pending issues.
  2. Then they move on to the report which was circulated by Test Lead to review and evaluate. In this process, defect description or Severity and Priority of the defect will be updated, if something is inappropriate.
  3. Triage Team in the meeting look into the issues and come to a conclusion on which defects should require immediate attention and which defects can be postponed for future releases.
    i. In the initial stage of the project, even the lowest priority bugs will be accepted to fix
    it. When the deadline is reaching, teams will concentrate more on high priority bugs and keep others on hold
  4. Based on the above two points, the status of the bugs will be updated and assigned to the respective teams
  5. Finally, Test Lead calls out for the meeting after taking a note of all the action items.

Post Meeting:

After the triage meeting, the Test lead shares the MOM (Minutes of the meeting) with the Triage Team.

Download Sample Defect Triage Report:

Click the below download button to download the Sample Defect Triage Report.

Bug Triage Report Format:

As I mentioned earlier, before every triage meeting, Test lead shares defect report to all the participants. Here is a sample format.

Fields involved in this report are as follows:

  • Defect Id: Defect Identifier is a unique number to identify the defect
  • Defect Description: Description of the defect
  • Created On: Date on which the defect was initially reported
  • Created By: Name of the person who reported the defect
  • Severity: Severity of the defect – how it affects the system
  • Priority: The priority code indicates the impact of this defect on the project:
    High – Extremely important, the project cannot be successful without this defect being resolved
    Medium – Important to project success, but a work around exists
    Low – Desirable, but with little impact to project success if the defect is not resolved
  • Status: Current status of the defect (New, In Progress, Under Review and Completed)
  • Assigned Date: Date on which the defect was assigned for resolution
  • Assigned To: Name of the person who is responsible for fixing the defect
  • Resolution: Description of the defect’s resolution
  • Resolution Date: Date on which the defect is to be resolved
  • Estimated Time To Fix: Estimated amount of time required to fix the defect
  • Actual Time to Fix: Actual time taken to fix the defect
  • Root Cause Description: State the cause of the defect


Bug triage meeting is an effective approach to manage and fix defects throughout the testing life cycle. The frequency of the Defect Triage should be weekly, monthly, every sprint (in Agile).

If you have any queries on Defect Triage, Defect Triage Process and Defect Triage Meeting, please comment below.

You may also like these posts:

Sharing is caring.

Share on facebook
Share on twitter
Share on linkedin

Like This Post?

We have a lot more where that came from?

We only send really good stuff occasionally, promise.

Rajkumar SM

Leave a Comment

Your email address will not be published. Required fields are marked *

Share on facebook
Share on google
Share on twitter
Share on linkedin
Share on whatsapp

Recent Posts:

Scroll to Top
API Testing eBook