2. AgileTrack Overview
3. Stories/Tasks/Defects
4. Iterations
5. Projects
7. Searching
A. XML-RPC Interface
5.1 Types
Project records are broken into three types. The different project record types are identical in functionality, but are classified by type simply to provide more structure to the potential project hierarchies that can be built. The different types and their potential uses are listed below.
Product
Product types are generally expected to be at the root of a project tree. A product will generally correspond to software application which is being developed and tracked within the system. When releases are planned, the release is generally expected to be tied to a product. Products often have sub-projects and components to provide a more granular breakdown of the requirements of the product and the tasks related to it.
Component
A component is intended to represent a piece or module in a software application or other project. Components can fit well into a tree structure made to represent a product and do well in helping classify issues. For example, an application may have a UI component, a database component, and a server component which could easily be represented in an AgileTrack project hierarchy.
Likewise, any component could have sub-components and projects as appropriate. For instance, in the example, the UI component could itself have a settings dialog sub-component as well as a main interface component. Components are intended to be used as such and tree structures representing a system can be built as desired.
Project
While "Product" and "Component" records are considered projects, a "Project" record is also provided. Project records are intended to be general purpose and used where products and components don't really fit. For example, a team may be responsible for server maintenance or IT infrastructure type tasks which are not related to a software product or component. Also, it may be that within a product a set of customizations for a particular customer need to be grouped together. In such a case, a project record is very appropriate.
 When in an open project, the project's type may be changed —
for example, a Component can be changed to a Product, etc. To change the project type, simply select a different type from
the "Type:" combo box. Before the change takes effect, it must be saved. |
 |