Submitted Jun 23 by Graham Robson
The recent implementation of Custom Fields is really good; I particularly like the leveraging of tagging to achieve it.
Of course, I'd like a bit more, specifically the ability to define a free form (non enumerated, free text) custom field. I'd expect this to be implemented in a very similar way with tags. An example us of this would be a customer reference number, as sometimes customers have and use there own internal tracking system.
A variant on this would be a custom field type like a URL, gain often used to cross reference. However, this might be better done with a real attribute of the ticket.

This feature would be very useful for our company to. we need to record details such as the customers help desk incident id etc.

And you can both be certain that it's coming. But no ETA yet.

Cool - thanks

Guys,
A quick update: We expect "free form" custom fields to debut within a month.

Thanks guys, that's great news. That was on the top of our feature wish list as well.

I believe we can strict this one off the requirements register with the latest customized fields update. Well done guys - thanks!

>A variant on this would be a custom field type like a URL, gain often used to cross reference
I'd like to second this!
We are currently heavily crosslinking bugtracking system with our support tracker.
Not to have this is really bit of a pain!

Bjorn - the fundermental constraint is that custom free form fields are exposed as forms, so they can't render links.
There is a workaround to this that Alexander helped us with. This involved enabling the exposure of the custom ticket fields place holders. We were then able to include the following snipet in the widget box
<h3>Links</h3>
<a href="{{ticket.ticket_field_<number here>}}">Bugzilla Hotlink</a>
You can obtain the number of the ticket field from the right-hand panel when looking at the custom field set-up.
It works good enough.

Thanks Graham. Yes, basically you can customize a lot with javascript, widgets and placeholders.