{"id":938,"date":"2022-12-04T17:32:56","date_gmt":"2022-12-04T17:32:56","guid":{"rendered":"https:\/\/www.softwaretestingstuff.com\/?p=938"},"modified":"2023-03-26T01:14:30","modified_gmt":"2023-03-26T01:14:30","slug":"bug-or-incident-or-defect-communication-triage","status":"publish","type":"post","link":"https:\/\/www.softwaretestingstuff.com\/2010\/09\/bug-or-incident-or-defect-communication.html","title":{"rendered":"Bug or Incident or Defect Communication & Triage"},"content":{"rendered":"\n

Test Manager\/Lead has to take the responsibility of communicating the defects to the respective Dev teams and all other stake holders. The process should be defined in such a way as depending on the severity of the defect the SLA for turnaround times should exist.<\/p>\n\n\n\n

The bug tracking & management tools should trigger an e-mail to the assigned team when the defect is assigned. If no tool is used Test leads will be sending e-mail communication to the Dev teams.<\/p>\n\n\n\n

While communicating bugs, always remember:<\/strong><\/p>\n\n\n\n