Custom Fields – FogBugz

Overview

If the case fields provided by Fogbugz do not quite serve your needs, you can add your custom fields in a matter of minutes, and track your case attributes. Custom fields can be any of the various types, including text, drop-down list, and date/time. This article provides information on how to add and edit a custom field, and details how custom field search works.

Adding Custom Fields
Editing Custom Fields
Searching Custom Fields

Back to top

Information

Adding Custom Fields

Go to Avatar Menu > Custom Fields.
Click Add New Custom Field.
Enter a Name and a Description for the field.
Select the Field Location.
Select the Data Type from the drop-down menu.
Set the visibility of the field by selecting the Projects and the Categories that you want to include your custom field.
Select the Modes of the field for the different instances of the cases.
Click OK.
To validate if the field is created, check whether it is listed under Custom Fields or not.

Once a custom field is created, you will be able to set values for it in the pop-up window of a New Case in a Project, given that the permissions are set accordingly. You will also be able to see a new column in the grid view.

Editing Custom Fields

Under the Configure column, click on the edit icon (pen and paper).
Proceed with the changes you want to do.

You can change all the options that you had set while you were adding the field.
Click OK.

Searching Custom Fields

Fogbugz provides suggestions with auto-complete in the search fields. Just start typing the custom field name, and let Fogbugz do the rest. Custom field names in search are case insensitive. They also ignore spaces and other non-alphanumeric characters.

The custom field Test Field autocompletes to TestField: in the search field. You can manually type testfield:[value] for searching any value in the custom field.

Fogbugz can also understand the FogBugz For Your Server format. For custom fields in FogBugz For Your Server, the search axis for any given field is the name of the field in the FogBugz UI, all lowercase, with any non-letter characters replaced by “x” (including spaces!).

Here are some examples:
“Fixed In” -> fixedxin:[value]
“My field 123*” -> myxfieldxxxxx:[value]
“Color 1″ -> colorxx:[value]
“Start Date” -> startxdate:[value]

Avoid search axis name collisions (“Color 1” and “Color 2” would each be “colorxx”) by carefully considering the names of your custom fields. Also, note that searching on date and date/time custom fields are only supported in Fogbugz.