prioritizing custom fields development

[Joel Peshkin]

Myk Melez wrote:
>
>     * product/component-specific custom fields;
>
   Yes, but a field should be able to be common to a bunch of products 
and ignored for others
>
>    *
>
>
>     * administer custom fields via a web interface;
>     * position custom fields at arbitrary locations in the "edit bug"
>       form;
>
   Or "hook" the field to let a custom template handle certain custom 
fields while leaving other custom fields auto-positioned
>
>    *
>
>
>     * single-select custom fields;
>       <https://bugzilla.mozilla.org/show_bug.cgi?id=287328>
>     * type-constrained plain-text custom fields;
>       <https://bugzilla.mozilla.org/show_bug.cgi?id=287330>
>     * multi-select custom fields;
>       <https://bugzilla.mozilla.org/show_bug.cgi?id=287332>
>     * "Bugzilla user" custom fields;
>       <https://bugzilla.mozilla.org/show_bug.cgi?id=287332>
>     * "Bug ID" custom fields.
>       <https://bugzilla.mozilla.org/show_bug.cgi?id=287334>
>
  Multi-bug-id fields
  Date fields
  Fields with group restrictions