Latest custom field revisions

[Gervase Markham]

Joel Peshkin wrote:
> 1) What happens when a bug is moved to a product on which the custom 
> field is not relevent and then is subsequently moved to a product where 
> it is?  (I suggest that the field be made invisible while in the product 
> where it is not irrelevent but not lost)

We already have an intermediate screen for moving between products; this 
should provide a warning that, if the operation is completed, the values 
of custom fields X, Y and Z will be lost.

> 2) Which name is used for the activity log?

Er... it's the same activity log as the normal one. Or, if you mean, 
what is the label in the "What" column, it should be the display name 
for the custom field.

> 3) What happens to the activity log on field rename?  (It should stay 
> consistent)

I would suppose that the name used would be the current display name 
corresponding to that field. So if you change a field to do something 
totally different, the activity log will look weird. So don't do 
anything that dumb.

> 4) In the standard templates, there will no doubt be a routine that 
> handles the custom fields.  If a site customizes the templates, can they 
> indicate that a field is "already done" so the routine skips a specific 
> field and leaves it to template customizations?

I think several people have already solved this one on the list :-)

Gerv