I figure that this field would be the easiest existing Bugzilla field to move into being a generic custom field, and moving it will give us a really good idea as to how the custom field implementation works.

(In reply to comment #1)isn't this a duplicate of 245375? > *** Bug 370182 has been marked as a duplicate of this bug. ***

(In reply to comment #2) > isn't this a duplicate of 245375? bug 245375? The bug about whining? No...

Bugzilla 3.2 is now frozen. Only enhancements blocking 3.2 or specifically approved for 3.2 may be checked in to the 3.2 branch. If you would like to nominate your enhancement for Bugzilla 3.2, set the "blocking3.2" flag to "?", and either the target milestone will be changed back, or the blocking3.2 flag will be granted, if we will accept this enhancement for Bugzilla 3.2.

I suppose this bug will not be fixed in time for 3.2 final, especially since it isn't yet ASSIGNED, has not even a first try at a patch, and a 3.2PR (or something) is already live at BMO. If the flags existed, I would set "wanted3.2" and "blocking-whatever" (the latter, for the next upcoming version) to question marks, especially since bug 16647, which is about including a Whiteboard input field on the "full" bug-entry form, is waiting on this bug for its fix.

We are going to branch for Bugzilla 4.4 next week and this bug is either too invasive to be accepted for 4.4 at this point or shows no recent activity. The target milestone is reset and will be set again *only* when a patch is attached and approved. I ask the assignee to reassign the bug to the default assignee if you don't plan to work on this bug in the near future, to make it clearer which bugs should be fixed by someone else.