Configuration Management
Issue Tracking
Issue Reports
|
Resolution
Definition: 'Resolution' codes give greater detail on how or why an
issue had its state set to 'Validate' or 'Closed'. |
There are many cases when teams (Dev leads, PM's, etc) want to know why an issue was finally closed. Avoid the temptation to create additional states, such as "closed: as designed', and "closed - do not fix." Instead, you can have as many resolution codes as you want.
The time to set the resolution field is when a developer addresses an issue and sets its state to
"Pending Validation." Not only does this let the tester know why it is now in their queue, but if the issue gets through QA, then the field does not need to be changed.
Similarly, if a manager determines that
the issue is not going to be addressed for whatever reason and directly closes
the issue from somewhere else in the workflow, a resolution code should be required (e.g.: state=closed, resolution=do not fix).
This values that you use for this field are likely to vary from one project to the next, with considerable
overlap.
The following Resolution codes are pre-defined in TeamTrack
| Resolution Code |
Notes |
| Code Change |
The code was changed to alter the product behavior. |
| Documentation Change |
The documentation was updated to be consistent with the actual product behavior. |
| Specification Change |
Also 'Fixed Indirectly'. No direct action was taken to fix this issue,
but it is no longer valid.
For example, a defect on a dialog where the dialog is no longer present
would fall under this code. |
| User Misunderstanding |
Similar terms are "Works as Designed".
Be careful that this issue is not prematurely "closed" using this resolution, only to spawn a new issue which is in fact a feature-request. |
| Not Repeatable |
Also 'CNR' for 'Can Not Reproduce'. Periodically, all
of these should be reviewed to see if a pattern is emerging. |
| Duplicate |
Indicates that this bug already exists. The other bug should be referenced in the notes, and this one closed. The status of the original bug to which this one refers is irrelevant. |
| Solution Found, Other |
Do not use this as a resolution code.
It communicates absolutely nothing.
Likewise, you should not have a default value for resolution code. To do so would allow the benefit of this field to evaporate. If you are going to use it, then use it all the time, and use it correctly. |
Contact Primary Goals for a detailed review of your issue tracking system, or for consultative assistance to ensure that you have a smooth deployment of your CM system.
|
