Add New Fields to FogBugz
The FogBugz interface does not allow the creation of additional case fields - that is, fields that you see when you enter a new case - nor the editing of existing case fields.
While source code modifications are not supported, this is a common enough request that this simple article has been written to get you started, if you're interested in pursuing this avenue.
There are 3 tiers of difficulty when you start considering your options:
Simple: Rename existing free text fields.
Change the name of either the Computer or Version field to be whatever suits your needs. This is done by changing the name of the field in the Site page -- then you're all set.
For example if you want the Version field to say "Client", to hold the name of the client, find the line that says "Extra Fields" and change "Version" to "Client".
Then if you want to run custom reports based on this field (e.g. in Access or Excel), the field in the database you want is the sVersion field in the Bug table.
Trickier (Database Modification): Add a new free-text field.
If you want to go one step further, add a new free-text field by modeling it on one of those two existing fields. Basically, copy and paste the existing version field and rename this new one Client, then add a new corresponding sClient field in the Bug table, and so on. You'd have to add it as a field in the database too, though. Just model your new field on the Computer or Version field.
Complicated: Add a new multiple-choice field, e.g. a droplist.
This is a fair amount more complex than either of the above options, in fact it is too complex for a knowledge base article and too complex for us to actively encourage. If you know ASP or PHP (depending on the platform on which you run FogBugz, naturally) you probably already know how to do this and don't need us to tell you anyway. If not, it would require ASP/PHP lessons to do this.
We ship the source code and you are free to modify it as needed. You can check it into a source control system like CVS or Subversion and let that system merge your changes with our changes when we release a new version. Disclaimer: modifying your source code may void the technical support portion of your maintenance contract.
