Custom fields

[Joel Peshkin]

Not  all Joels agree....

1) Sites will frequently need to add some special field to make THEIR 
customer happy.  It is likely that they will need to do this and then 
tweak templates to make this vary on a per-product basis.  Just because 
any site specific thing that is needed by contributors with sufficient 
clout DOES become a standard field should not imply that the others are 
irrelevent.

2) About once a week, I see an RFE response that says.... "This should 
not be a feature, you should wait for customfields and do it that way"
    Do we plan to dust off all of those and re-evaluate that position? 
 Won't the resulting heap of fields really clutter Bugzilla?

I think customfields is a highly valuable feature.  It may not be 
necessary to make it all controlled by a pretty GUI, but we should put a 
good set of hooks in for sites to add their own fields without setting 
themselves up for merge problems down the road.  Basically, we should 
use a similar approach to what Gerv did in CheckCanChangeField() where 
we assume that someone at the site can program, but not that they are 
staying up-to-date on everything happening in the tree.

-Joel