How to conduct bug triage?

Required tools

• Azure DevOps — Registration and follow-up of non-conformities in ongoing customer projects.
• Dynamics 365 — Recording deviations in completed customer projects.
• Power BI — Reports deviations collectively to the customer and ProsessPilotene management.

Register and classify the case

1. 1.Report the error

   Register the nonconformity in Azure DevOps for an ongoing project, or in Dynamics 365 for a completed project.

2. 2.Assess whether the case is small or large

   Classify the case: a small case is normally resolved within four working hours and is considered a pre-approved call-off, while a large case requires more than four hours.

3. 3.Start immediately in the event of a critical operational deviation

   If the issue is a business-critical incident, start working to resolve it immediately and keep the customer informed throughout—the issue will then be considered an approved call-off.

Prioritize and submit for correction

1. 4.Create a simplified estimate for large, non-operationally critical issues

   For a major issue that is not operationally critical, prepare a simplified estimate of the work and have it approved by the customer before resolving the issue.

2. 5.Prioritize the case

   Have the test manager classify and prioritize the issue against other incoming work in the project.

3. 6.Send the case for correction

   Link the issue to the correct task or user story, and forward it to the CRM consultant who will fix it.

Follow up until closure

1. 7.Test the fix

   Have the test lead or test team verify that the fix resolves the reported defect.

2. 8.Report the non-conformity

   Ensure that the non-conformance is reported so that it is included in Power BI reporting to the customer and management, providing a basis for continuous improvement.

3. 9.Close the case in the correct system

   Close the case in Azure DevOps for ongoing projects, or in Dynamics 365 for completed projects, with a clear status.