2. AgileTrack Overview
3. Stories/Tasks/Defects
3.2 Issue List View
3.3 Creating Stories/Tasks/Defects
3.4 Templates
3.5 Classification
3.6 Assignment
3.7 Status/Completion
3.8 Comments
3.9 History
5. Projects
7. Searching
A. XML-RPC Interface
3.7 Status/Completion
Much has been discussed regarding how to handle creating, classifying tasks, and assigning issues within AgileTrack. While all of that is important, ultimately issues must be completed and there must be a way to track the status of issues in the system.
State
All issues in AgileTrack have a "State". The "State" is a short description of the status of the issue and is intended to reflect the lifecycle of an issue. Therefore, an issue generally has states that are intended to represent the progression of the issue through its lifecycle. For example, a task could progress from "Prepare" to "Open" to "Complete" by manipulating its state in AgileTrack.
Unit Tested
Because automated testing is considered an essential part of Extreme Programming and effective software development in general, issues in AgileTrack have been given a simple flag to indicate whether unit tests or other automated tests have been implemented in conjunction with the completion of an issue. Not all tasks can be unit tested, but the presence of the "Unit Tested" flag is meant to serve as a reminder of the importance and value of automated testing in agile software development.
Verified
An issue reaches the end of its lifecycle once it is verified as complete. The "Verified" flag essentially marks an issue as closed. Once closed, an issue will automatically be excluded from the main issue list in the Issues tab after a week of no more changes to the record. So, ultimately, being "Verified" is the last step in the lifecycle of an issue in AgileTrack.