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

Project Portal
| See Also MSF for Agile Software Development Bug Work Item |
| Close a Bug Tester
|  | Participating Roles Responsible: Tester
### Overview A bug may be closed for several reasons. Once closed, no more work is done on the bug during the current iteration. Valid reasons for closing a bug include that it is fixed, deferred to another release, demonstrated invalid, not reproducible, or a duplicate of a bug already logged. Closing bugs usually occurs during triage or to verify a fix. # Entry Criteria The bug is set to a resolved state and appears in the build notes of a team build. The bug has been identified in triage as not worth fixing in this release. # Activities
1 | Verify a Fix | Attempt to reproduce the bug. Look for unexplained behavior. Get more information on the bug. Reassign the bug.
2 | Close the Bug | Confirm the bug is a duplicate. Report the bug is not fixed. Report the bug fixed.
# Exit Criteria
| The bug is closed with the appropriate reason code.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |