What are bugs? Are bugs really work items?

[Gervase Markham]

> Christopher Hicks wrote:
>> Thanks for all the folks who have sent me private notes of support in 
>> this process.  And particular thanks and apologies to the bugzilla 
>> developers I've annoyed in trying to get task management implemented 
>> in bugzilla.

I seem to have missed the original of this... but I don't think anyone's 
annoyed. I just wanted to point out the difference in goals to make sure 
that no-one was misled.

We have enough trouble keeping up with the bug fixes and feature 
requests to make Bugzilla a world-class bug-tracking (or defect-tracking 
- call them what you like) system. This is demonstrated by the fairly 
slow pace of development and the difficulty in getting reviews. Trying 
to be different pieces of software as well would just lead to developers 
being spread even more thinly than they currently are.

Joel Peshkin wrote:
> Actually, it would be best to start by identifying the places where 
> adding new hooks to Bugzilla makes it easier to tie in functionality 
> that the standard Bugzilla does not want.  The addition of templates, 
> modular authentication, template hooks, template plugins, etc... all 
> move the underlying Bugzilla project in a direction that makes it easier 
> to do this sort of thing.

Absolutely. No argument from me on this front.

> Aside from a few custom fields and some template changes, I suspect that 
> one of the major things needed for work items is to have a stronger 
> sense of workflow.  This is something that is useful to the core 
> Bugzilla project as well.

More agreement :-) I'm all for cust res. and cust. statuses.

Gerv