On Tuesday 28 February 2006 13:58, Myk Melez wrote:
vladd at bugzilla.org
Wed Mar 15 17:10:40 UTC 2006
The biggest problem is reviewing, integrating and QA-ing such a large
chunk of code.
Doing it one-step-at-a-time speeds up the process, at least that was the
direction in which we were going with this, last time I checked.
Gregary Hendricks wrote:
> On Tuesday 28 February 2006 13:58, Myk Melez wrote:
>> Thanks all for your feedback. Based on what you've told me and my
>> sense of the project, I've roughly prioritized tasks into the
>> list, where the tasks appearing earlier are higher priority:
>> 1. custom fields appearance on search, bug list, change multiple
>> bugs, long list, and printable pages;
>> 2. ability to list and delete custom fields via the
>> 3. boolean fields;
>> 4. web interface for managing custom fields;
>> 5. ability to position fields at arbitrary places on the edit
>> bug page;
>> 6. type-constrained plain-text fields;
>> 7. single-select fields;
>> 8. user fields;
>> 9. bug fields;
>> 10. multi-select fields;
>> 11. date fields;
>> 12. ability to restrict fields to specific product/component
>> 13. ability to restrict fields to specific user groups;
>> 14. multi-user fields;
>> 15. multi-bug fields.
> I am curious about something. At bugzilla.novell.com we implemented a
> field patch some time ago. We got the code from one of the custom patch
> made it into a module, and have been using it since day one. Of the 15
> listed here it does almost everything but the command line interface
> (at least
> for bugs). It has a GUI interface for managing the fields, which show
> up in all
> the places listed. And though we don't have support for user fields
> (not sure
> what is meant by that), it would probably not be too hard to extend.
> We offered it back but were told that was not the direction Bugzilla
> was going.
> This was back in the days we had the raging debate over custom field
> So my question is, has there been a change of direction?
> Because this seems to be exactly what we have already.
> Greg Hendricks
> To view or change your list settings, click here:
More information about the developers