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.3 Creating Stories/Tasks/Defects
When ideas come, it is useful to be able to log them immediately so that they are not forgottern. The details can often be worked out later, but remembering the idea itself is the trick. In AgileTrack, there are essentially two ways to create new issues. The Create tab is the most obvious location for creating new issues, but the various issue lists from the different record views also allow for new issues to be created.
Create Tab
Because creating stories and tasks, etc. is considered a very frequent and important function, it is made available in it's own tab. The Create tab is fairly self explanatory. All new issues require a title and a type — all other information is optional. New issues are automatically assigned to the creator of the issue, but the owner and other fields can be can set when the new issue is being created. After filling at the fields, clicking the "Create" button will save the new issue, and clear the fields in preparation for another new issue. The "Clear" button will reset the fields.
Note that after creating a new issue, the main issue list will need to be refresh before it will be visible.
The Create tab also has issue templates which can be created and deleted. Templates are covered in their own section of this chapter.
Edit Mode
When the main issue list edit mode is enabled, new issues can be created. Directly above the issue filter combo boxes, is the text field for entering the new issue titles. To the left of the issue title, the type for the new issue can be selected — e.g. Story, Task, Defect, etc. After entering the issue title, pressing Enter, or clicking on the "Create" button will create the new issue.
It is important to understand that the new issue will be categorized according to the filter items currently selected. For example, if an iteration is selected to filter the visible issues, the new issue will be automatically assigned to the selected iteration. Likewise, the project and user filters will also be used to automatically assign and owner or project to newly created issues.
Iteration/Project Views
When viewing iteration and projects, the Issues tab for and iteration or project has a text field provided at the bottom of the list. The text field functions the same as that found in the edit view described above. That is, when "Create" or enter is pressed, a new issue will be created and automatically assigned to the corresponding iteration or project.
Sub-Tasks
Sub-tasks can be created by first opening an issue. Then select the Sub-Tasks tab from the issue view. From that point, sub-tasks can be created by using the text field at the bottom of the list, as has been described for the other views above.
It is also possible to make move tasks and sub-tasks to other issues using drag-and-drop functionality from the Issues tab. When in edit mode, tasks can be dragged
It is possible to move tasks and sub-tasks to
other issues using drag-and-drop from the Issues tab. When in edit mode, tasks can be dragged
and dropped. If a tasks is dropped on another issue, it becomes a sub-tasks of that issue. If a sub-task
is dropped on its parent, it no long is a sub-task. |
![]() |
It is possible to move tasks and sub-tasks to
other issues using drag-and-drop from the Issues tab. When in edit mode, tasks can be dragged
and dropped. If a tasks is dropped on another issue, it becomes a sub-tasks of that issue. If a sub-task
is dropped on its parent, it no long is a sub-task.