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.1 Types
There are three types of issues that can be recorded. The different record types are nearly identical in functionality, but serve different purposes and differ int subtle ways.
Story
Story records are meant to represent user stories in Extreme Programming. More plainly, a story is like a feature in a software application. As a feature, it is usually independant of other features and requires new coding to complete. It may have be large and complex, but may also be small and simple. In general, it can also be recommended that a story represents a use case for a product, and the story's scope is limited.
Task
In AgileTrack, an issue is intended to be categorized as a task if it is an issues which doesn't represent a feature of a product, nor a defect. For example, "Configure a automated build environment" would be a likely title of a task as it is necessary work, though not tied directly to a product feature. Task records may be used at a user's discretion. Extreme Programming would suggest that such tasks would always be related to a user story.
Stories, tasks, and defects in AgileTrack may also all have sub-tasks defined. A sub-task is a task record which is tied to a particular parent task. In an Extreme Programming environment, sub-tasks would make up the implementation details of a story. In AgileTrack, sub-tasks have a few additional configurable behavior properties related to iteration planning, and classification.
Defect
Defects are expected in all development projects and have special properties. It is also useful to classify defects separate from stories or tasks for identification and planning purposes. In weighting the importance of fixing defects, it is useful to have a method of rating them. With that in mind, AgileTrack provides the additional classification fields of frequency and severity for defect records. Beyond that, defects function identically to stories.
 When in an open issue, the issue's type may changed —
for example, a Story can be changed to a Defect, etc. To change the issue type, simply select a different type from
the "Type:" combo box. Before the change takes effect, it must be saved. |
 |