If the case fields provided by Manuscript don’t quite serve your needs, you can add your own custom field (previously provided by the Custom Fields Plugin) in a matter of minutes. The field can be any of several types including text, drop-down, and date/time.
You can access the Custom Fields management page by going to Avatar menu > Custom Fields. On this page you can “Add New Custom Field” or click the “Edit” icon in the Configure column to change the configuration of an existing custom field.
Once a custom field exists, you’ll be able to set values for the new field when editing a case. You will also be able to see a new column in the grid view, and even search for cases based on the values of their custom fields!
In order to control the visibility of a custom field, you’ll need to edit the properties of the custom field. To do this, click the “Edit” icon in the Configure column for the field in question > then under “All Projects” uncheck the checkbox, and select the applicable projects.
Searching Custom Fields
In Manuscript, custom fields will be suggested with auto-complete. Just start typing the custom field name, and let Manuscript do the rest. Custom field names in search are case insensitive and ignore spaces and other non alphanumeric characters. For example:
The custom field “Fixed In” will autocomplete to “FixedIn:”and you can manually type “fixedin:”
The custom field “My field 123*” will autocomplete to “Myfield123:” and you can manually type “myfield123:”
The custom field “Color 1” will autocomplete to “Color1:” and you can manually type “color1:”
Note that Manuscript can also understand the FogBugz For Your Server format, below.
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!)*. Examples:
“Fixed In” search for -> fixedxin:”foobar”
“My field 123*” search for -> myxfieldxxxxx:”something”
“Color 1″ search for -> colorxx:”blue”
“Start Date” search for -> startxdate:”today” **
* Note that this can lead to search axis name collisions (“Color 1” and “Color 2” would each be “colorxx”), which may cause your search results to be incorrect. You should avoid this by carefully considering the names of your custom fields when creating them.
** Searching on date or date/time custom fields is only supported in Manuscript.