1

Determine if the Bug is a Duplicate

• Before opening a new bug in the bug tracking system, examine the database to see if a similar problem has already been identified.
• If the problem is already reported and the bug is open, update the bug tracking form as appropriate.
• If the problem is already reported and the bug is closed, change the state of the bug work item from Closed to Reopen.
• Add new information and document the new steps to reproduce the bug.
• Document the build number where the incorrect behavior was identified.

1

Log a New Bug

• If the bug is unreported and can be reproduced, enter the steps to reproduce the bug and details about the results of what happens when the steps are followed in the work item.
• Include as many details as possible to help the team responsible for prioritizing the bug understand the problem.
• Where applicable, attach the test case, test results, test configuration, scenario, or quality of service requirement to the bug report.

2

Assign the Bug

• Determine the main area of the problem. If more than one area could be the cause, choose one of them.
• Assign the bug to the owner of the affected area of the application.
• Save the bug to the bug tracking database. 

The bug is properly entered into the bug tracking system and contains the information necessary for triage.

The bug is appropriately assigned.