A tracker is a collection of related artifacts that describe work to be done or
issues to be resolved. Every project should have one or more trackers.
When you start a tracker, you decide which fields will be used, who will use
them, and how they will use them.
Organize tracker fields
Most tracker artifacts ask the user for a lot of information. You can arrange the input fields in columns and rows to make it easier for users to find the fields they need.
Configure tracker units
You can estimate the value of efforts meaningfully in the form of units using the TeamForge tracker.
Create a tracker work flow
To channel project members' work on tracker items, set up rules for how a tracker item can move forward.
Set default tracker columns
Choose what information is visible by default to users of your project when they open a tracker or planning folder.
Create a tracker
Create a tracker whenever you need to report and track bugs, feature requests, support requests, or any other type of issue where ownership, status, and activity must be managed.
Clone a tracker
To save efforts in duplicating a tracker within the project and across the projects, choose cloning options available in TeamForge.
Enable or disable fields
If a tracker field is disabled, it does not appear on the Artifact page. Most fields can be disabled.
Create your own tracker fields
To track data that is not captured by the default set of fields, create new fields that fit your project's purposes.
Configure tracker "Select" field values
To help users provide meaningful information, supply them with useful field values to choose from in the input fields in the tracker entry form.
Change a tracker
A tracker's real-world uses often outgrow the name or description you gave it when you created it. When that happens, it's a good idea to update the tracker to reflect its changing role.