 |
Activity:
Close Bug
 |
|
Participating Roles
Responsible:
Tester |
A bug is closed for many reasons. In a simple case, the bug was verified as Fixed and can also be closed. However, a bug can be deferred to the next version of the product, proven not to be reproducible, or confirmed as a duplicate. Each of these reasons must be documented and closed properly to ensure there is no confusion about why the bug is closed.
Entry Criteria
When:
- Bug resolution has been verified.
Dependencies:
- Bug: The bug resolution is verified and ready to be closed.
Sub-Activities
|
|
1 |
Change the State of the Bug |
- If the bug work item is a duplicate, close the bug as a duplicate, identifying the duplicate bug work item ID.
- If the bug is not to be fixed, close the bug as Won't fix.
- If the bug resolution was that it was not reproducible, and the bug is indeed no longer reproducible, close the bug as Not reproducible.
- If you verified the bug fix, close the bug as Fixed.
|
|
2 |
Update Bug Description |
- If the bug was verified as fixed, be sure to fill in the build number on which you tested it.
- Give complete information on why the bug was closed. If the team needs to revisit the bug later, this information will help avoid rework.
|
Exit Criteria
 |
Bug is closed. | |
 |
Program Management
