prioritizing custom fields development

Myk Melez myk at
Tue Feb 28 22:33:31 UTC 2006

Gervase Markham wrote:
> Myk Melez wrote:
>>    4. web interface for managing custom fields;
> As others have said, this seems too high to me. Custom field management is a rare operation. Would a command-line client really be so troublesome?
Operations like adding, listing, and deleting custom fields are likely 
to be relatively easy to implement in a command-line tool (and hence are 
prioritized more highly), but a good UI for making modifications to 
existing fields seems relatively complicated to implement on the command 

This item might be better described as the prioritization of the ability 
to edit custom fields, for which a web interface is the path of least 
resistance to a usable interface.  Of course, you might still consider 
this functionality to be prioritized too highly.

>>    5. ability to position fields at arbitrary places on the edit
>>       bug page;
> Presumably by this you mean "ability to add code to a template such that Bugzilla notices a custom field has been specifically placed and doesn't reproduce it in the generic area"?
Most likely that's what I mean.  Arbitrary positioning itself will 
certainly involve adding code to templates, and telling Bugzilla which 
fields are arbitrarily positioned, so that it doesn't reproduce them in 
the generic area, will probably also involve template code (perhaps the 
two can be integrated), although there are other possibilities (f.e. 
listing arbitrarily positioned fields in a site parameter), and I 
haven't thought through the problem yet in detail, so I can't say for sure.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the developers mailing list