Predefined fields
An organization admin can add predefined fields. They are indexed and can be searched without using the database field name.
If you frequently use reporting with your data, predefined fields simplify the document type's underlying schema and make is easier to use those fields in reporting.
When adding fields, you must select the database location where the lookup value is stored from predefined fields. This selection doesn't affect users. However, custom report writers must know the mapping of the fields to the database.
These are the predefined fields you can choose:
Type | Details |
|---|---|
Text | Rich text can be enabled in text fields. |
Dates | Each field (date1 through date5) limits the user entry to a valid date and provides a pop-up calendar picker. |
Integer | The fields originalEstimate, remainingEstimate, and timeSpent allow only whole number positive numerals. |
Flag | Flag fields are displayed as checkboxes. By default, all flags are marked as No (false). |
String | Includes the predefined fields Short Name, ID, and string1 through string15. |
Pick list | In the Add field window, fields such as status, priority, and lookup 1–10 prompt you for a has been pick list. If that option isn’t available, you select a non-pick list type from the drop-down list. Once a predefined field is used for a pick list, it's no longer available in the list. If additional fields are needed, use custom fields. |
Release | Each pick list is populated by the list of releases created within each project. Some item types are configured with a release field by default. If the release field is removed from the item type, it becomes available in the predefined field list. |
User | Item types with a user field include a pop-up list of users. Only one user can be selected from the list. |