Issues

In TC Tracker, an Issue refers to either a Bug Report, Feature Request, Enhancement, Task, Work Request, Information Request, Change Request, Requirement, or Idea. All contain very similar information, but the distinction makes it easier to visually distinguish between the two in our user interface. Although the field descriptions may differ for each type, the data stored is identical in all cases.

In most cases, the options available for any key field are selected from a predefined list (configurable). Free-form fields allow you to enter plain text, or text formatted using HTML.

All changes to key fields are recorded in a History list which cannot be modified. This list provides valuable information about the progress of the Issue.

The information stored for Issues includes:

Area (List)
This is the functional area within the project that this Issue references.

Description
Basic description of the Issue. Displayed in the list view.

Origination

The Origination section defines how the issue was raised, by who, and what priority was assigned to it.

Submitted by

Displays the name of the user that created the Issue (cannot be modified)

Submitted on

Displays the date that the Issue was created (cannot be modified)

Priority (List)

Specifies the priority of the Issue.

Complete by

Specifies the date that the issue should be completed by. If an issue is unresolved after this date, it is highlighted in the listview.

Requested by/Reported by

Freeform text that allows you to define who requested the change or reported the bug.

Severity (Bugs)(List)

Specifies how serious the reported Bug is.

Reported in Version (Bugs)(List)

Defines the Version of the product that the issue was reported in. If Tracker is integrated with Team Coherence, a list of existing Version Labels will be displayed.

Resolution

The Resolution section describes the current and final status of the Issue.

Assigned to (List)

Shows who the Issue is currently assigned to.

Current Status (List)

Specifies the current status of the Issue.

Completed

Specified the date that the Issue was marked as 'Completed'. This field cannot be modified, but changing the Status to another value (other than 'Verified') will clear this date. The change will be recorded in the History.

Completed By (List)

Specifies the User that marked this issue as 'Completed'. Setting this field, by whatever method, will set the Completed date value.

Verified

Specified the date that the Issue was marked as 'Verified'. This field cannot be modified, but changing the Status to another value will clear this date. The change will be recorded in the History.

Verified By (List)

Specifies the User that marked this issue as 'Verified'. Setting this field, by whatever method, will set the Verified date value.

Implemented in Version (List)

Defines the Version of the product that the issue was implemented in. If Tracker is integrated with Team Coherence, a list of existing Version Labels will be displayed.

Closure Category (Bugs) (List)

Specifies a category that can be used for reporting.

Request / Report

Free-form notes about why the issue was raised. This field can be either plain text, or can be formatted using HTML to include tables, different fonts, and colour.

Implementation Notes / Notes

More free-form notes to allow you to specify how the issue was implemented, or record any other information.

New Ideas / Other

More free-form notes to allow you to specify any new ideas that arose during the implementation or resolution of this issue. This field can be included in the page report.

Resolution

Yet another free-form note field. This one can be used to describe how the issue was resolved.

Attachments

This 'field' allows you to attach documents to the issue. In particular, it allows you to directly link an issue to one or more Team Coherence archives. Normal files, when associated with an Issue are not stored as part of the Issue, so avoid using local pathnames or these files may not be accessible to others. To make sure that all documents are accessible to others, archive them using Team Coherence before adding them. In this way, you also get a history of the changes to the documents.

Images

Images can be stored against an Issue. In most cases, a picture can better describe why an issue was raised than words. Images are stored as part of the issue, so are available to anybody who can view the Issue. Images can be pasted from the clipboard as well as being loaded from file. All images are compressed at the server-side.

History

The history 'field' displays all the changes made to key fields during the life of the Issue. The details cannot be modified and provide a valuable history of who did what in the resolution of th issue.