Project Field Maintenance

Project fields are used to track information for Issues in the current Project. The fields configured here are displayed in the Issue Information section of the Create Issue and Edit Issue pages. They are also available automatically as criteria for searches, reports, escalation rules, and auto-assignment.

If the Project Setup Wizard was used to create the current Project, the default fields for the template are displayed in the dialog box.  If no wizard was used and this is the first time you have visited this page, the dialog box is blank.  Create, edit, delete, and re-order fields on this page.

This page is accessed by selecting Administration | Project | Field Maintenance from the FootPrints Toolbar.

Note

For Service Level Agreement (SLA) maintenance, an existing drop-down field is the basis for the SLA.  The original field is created on the Field Maintenance page.  However, once the drop-down has been created, additional SLA options for the drop-down are not added on the Field Maintenance page.  To add another service level, go to the SLA setup page and add the additional option there using the Add new SLA button.  This adds the new option and allows you to configure it at the same time.

The following topics are covered in this section:

• Adding Fields
• Drop-down and Multi-select Fields
• Edit Field
• Delete Field
• Re-order Fields
• Advanced Field Permissions
• Insert Text/HTML Headers

For information on field types, refer to Field Types.

Restrictions

With respect to any size limits for fields, there is very little danger of exceeding the limits of most databases.  Nevertheless, there are limits of which administrators should be aware.  When the number of fields in an individual project grow into the hundreds, performance may begin to degrade or data may begin to be truncated.  Administrators should at least be aware of this possibility.  There are two ways in which field proliferation could get out of hand.  One is through the use of field dependencies.  The other can occur by using field-level permissions to combine multiple projects into a single project.  Both of these features are extremely valuable and help to simplify life for the user.  Administrators should not in any way avoid using these features.  They are mentioned here only because of the slim chance that they could cause a problem through field proliferation.

Reserved Words

For a list of FootPrints Reserved Words, open the mrReservedWords.pl file in the FootPrints/cgi directory.