Triage is a French term that means to separate, select and sort. In the testing domain, this term defines the priority and severity of the bugs found in a project. It is the most suitable for projects where you find multiple bugs in huge volumes. A lead or the project manager in the QA domain organizes a bug triage meeting to sort the bugs into varied categories and decide which one would get solved on priority. How often the leads conduct these meetings depends on the project situation. o Bug triaging steps involve the following things: Check the bug description given by the test engineer to verify if it is enough for the developers to understand the flaw. If this information is not enough, it goes back to the test team, and they get asked to give a better and more detailed description. Check if the bug gets categorized in the apt project module and segregated under the least or the top priority index. This clarity is significant as the developer needs to understand what they should solve first. The test leads check to ensure that the bug is not duplicated and has a unique place in the module in which it is mentioned. Furthermore, they are also right about the appropriate keyword to bug. They assign bugs to the team members who they feel should handle them. They do so by either mentioning the expert's name in front of the bug or placing their names in the cc. These are the basic guidelines of bug triage and the process that test leads follow during triaging. After every meeting, triage reports get generated to keep track of what happened during the triaging process. Moreover, bugs keep arriving during a process, so these meetings are recurring, and so is the report generation.