The release of Bugzilla 3.0 added the ability to create Custom Fields. Custom Fields are treated like any other field - they can be set in bugs and used for search queries. Administrators should keep in mind that adding too many fields can make the user interface more complicated and harder to use. Custom Fields should be added only when necessary and with careful consideration.
Before adding a Custom Field, make sure that Bugzilla can not already do the desired behavior. Many Bugzilla options are not enabled by default, and many times Administrators find that simply enabling certain options that already exist is sufficient.
Administrators can manage Custom Fields using the "Custom Fields" link on the Administration page. The Custom Fields administration page displays a list of Custom Fields, if any exist, and a link to "Add a new custom field".
To add a new Custom Field, click the "Add a new custom field" link. This page displays several options for the new field, described below.
The following attributes must be set for each new custom field:
Name: The name of the field in the database, used internally. This name MUST begin with "cf_" to prevent confusion with standard fields. If this string is omitted, it will be automatically added to the name entered.
Description: A brief string which is used as the label for this Custom Field. That is the string that users will see, and should be short and explicit.
Type: The type of field to create. There are several types available:
|Large Text Box: A multiple line box for entering free text.|
|Free Text: A single line box for entering free text.|
|Multiple-Selection Box: A list box where multiple options can be selected. After creating this field, it must be edited to add the selection options. See Section 3.11.1 for information about editing legal values.|
|Drop Down: A list box where only one option can be selected. After creating this field, it must be edited to add the selection options. See Section 3.11.1 for information about editing legal values.|
|Date/Time: A date field. This field appears with a calendar widget for choosing the date.|
Sortkey: Integer that determines in which order Custom Fields are displayed in the User Interface, especially when viewing a bug. Fields with lower values are displayed first.
Can be set on bug creation: Boolean that determines whether this field can be set on bug creation. If not selected, then a bug must be created before this field can be set. See Section 5.6 for information about filing bugs.
Displayed in bugmail for new bugs: Boolean that determines whether the value set on this field should appear in bugmail when the bug is filed. This attribute has no effect if the field cannot be set on bug creation.
Is obsolete: Boolean that determines whether this field should be displayed at all. Obsolete Custom Fields are hidden.
As soon as a Custom Field is created, its name and type cannot be changed. If this field is a drop down menu, its legal values can be set as described in Section 3.11.1. All other attributes can be edited as described above.
It is only possible to delete obsolete Custom Fields if the field has never been used in the database. To remove a field which already has content, mark it as obsolete.