The Road to 2.18 - Customfields

[Stuart Donaldson]

Jon Tollefson wrote:

>On Fri, 2004-03-12 at 13:01, Christopher Hicks wrote:
>  
>
>>On Fri, 12 Mar 2004, Joel Peshkin wrote:
>>
>>    
>>
>>>In many ways, Sean's approach is cleaner than addind a bunch of columns
>>>to the tables,
>>>      
>>>
>>For instance, we would need to avoid custom columns conflicting with 
>>future official columns which implies munging the custom columns with ugly 
>>names and ugly is bad.  :)
>>    
>>
>
>Might we want some of the official columns(eg. status whiteboard,
>keywords, target milestone, qa contact, etc) to be implemented as custom
>fields?  Then sites could easily remove those fields if they didn't need
>them.
>
>  
>
There has been concern about the number of tables and left-joins 
involved with custom fields.  There is also some interest in per-project 
custom fields.  Personally, I just need a couple of global fields, and 
do not need the per-project fields.

Does it make sense to have two categories of fields.  Global, and 
Per-Project?  The global fields could be added columns in bugs table.  
That way existing columns could be easily incorporated as custom global 
fields.