Each FIT template is packaged with a unique set of default fields to help ease the installation of the product and allow users to get up and running in the quickest amount of time.
The default fields can be customized using the "Default Fields" menu, where there are also options to disable them.
In addition, their access attributes can be changed in the "Field Control" menu. For example, they can be changed to hidden / readonly if undesired.
In some cases, customers choose to rename them by changing the text strings in the "Customize Strings" menu.
Unfortunately, the default field types cannot be changed (ie: Area is a drop down item not a text string).
If you wish to change a default field type, you will need to disable or hide the existing one and then create a new custom field.
| Subject | A brief summary of the issue which can be read quickly in the main menu list. |
| Assigned To | A dropdown list of all visible userids in the system. This field is used to select the individual who is currently responsible for the given issue. It is a good idea to make this field "Always Mandatory" so that it is always current and never mistakenly skipped on an edit to the issue. |
| Project | A development team can easily be involved with a number of different products or projects.
The project field allows issues to be grouped together as a set. The project field is special as it can be used to define issue visibility in groups.
Therefore, it is not a good idea to rename this field unless you are sure you know what you are defining. It should be used for group segmentation. |
| Status | The status fields refer to the different states that an issue can assume. The idea is to have each bug run through these states until it is eventually fixed and closed. The default status fields (in order) are : Open, Ready For Retest, Rejected, Deferred, Closed. |
| Priority | A unique integer value (number) must be specified for each priority. When priorities are displayed, they are sorted by this numeric value. The priority field is used to rate the importance of an issue. This allows a team to sort issues according to importance, and fix the most important problems first. The default setup is : 1 - Emergency, 2 - High, 3 - Medium, 4 - Low, 5 - Very Low, 6 Change Request. This field is also commonly used by the Rank feature to escalate issues. |
| Environment | An environment refers to the system where the issue was discovered. The purpose of this field is to provide helpful information to the individuals that will eventually try to reproduce the bug and fix it. Typically, this includes the type of machine and OS being used (ie: Windows, Unix, Mac). |
| Version | A version can refer to the Environment Version or to the Version of the item that is being tracked. This field is a text string by default and can not be changed. If you desire another field type, the best solution is to disable this field and create a new custom field. |
| Area | An area refers to the area within the product where the issue was found. This information can help any individuals further on in the cycle, so that they have enough information to work on the problem. |
| Description/Comment | This field allows users to enter a description of every modification made to an issue. In many cases, this field is renamed to Notes or Comments. It is by default a history field so that every historical update is shown with the description applicable to that change.It is a unique field in that there is no overall value that is shown in the details section of the view/edit bug screen. |
| Notify list | A list of individuals to get notified whenever the given issue is modified. Please see discussion on Notification Rules. |
| Requested Due Date | A date field that can be used to record a Due Date for the issue. Commonly used when creating events to notify about overdue or upcoming due dates.
|
| Actual Completion Date | A date field commonly used for recording the date an issue is Closed or when work is completed.
|
| Percent Complete | A numerical field used for recording the percentage of work that is complete.
|
| Estimated Hours | A numerical field used to record the number of hours that an issue is estimated to require.
|
| Actual Hours | A numerical field used to record the number of hours actually used.
|
| Parent | The parent field allows you to link an issue to a related parent issue. When an issue becomes a parent, it will then list all children in it's details section. Children are listed with field values in a similar way to the normal main menu (see child example below).
Additional Properties :
A parent issue can not be closed until all of it's children are closed.
The "Requested Due Date" and "Actual Completion Date" fields become readonly and are calculated as the earliest due date of the children
The "Estimated Hours", "Actual Hours" and "Percent Complete" fields become readonly and are calculated as a sum of the values for the children.
|
