Overview |  | Roles |  | Work Items |  | Views |  | Index |  | Glossary |

Project Portal
| Activity: Reopen a Bug
Tester
|  | Participating Roles Responsible: Tester
### Overview Reopening a bug in a bug tracking system indicates that the bug has not been fixed correctly or the fix has been removed. A reopened bug needs to be revisited and repaired after additional information is documented. It might be necessary to reopen a bug after it has been closed. If, after a bug has been verified as fixed and closed, it is found to fail in a test case, the bug is reopened to be fixed again. Reopening a bug rather than creating a new one leverages the recorded information from prior work. # Entry Criteria The build that exhibits incorrect behavior is identified. The expected behavior is identified. The test cases that exercise functionality related to the bug are identified. The existing bug is identified. # Sub-Activities
1 | Update Bug Description | Document the specific problems with the fix in the bug description. Document new steps to reproduce if they are different from the original steps. Document build number where the incorrect behavior was identified.
2 | Mark the Bug as Open | Change the state of the bug record from closed to the reopen or new state to allow the triage process to consider it.
# Exit Criteria
| The bug is reopened in the bug tracking system with an updated description of the incorrect behavior.
| The bug is ready to be triaged and reassigned.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |