What are bugs? Are bugs really work items?

[Max Kanat-Alexander]

On Tue, 2004-10-19 at 04:29, Christian Robottom Reis wrote:
>     - Bug type: An enum of localconfig-defined values that can be used
>       to define what that bug represents [snip]

	I've certainly also considered adding this to my local Bugzilla, but
I've wondered what real process advantage it gets me. Is it somehow
better than just having separate components for those types of things,
per-product? 

	I mean, the reason that I'd want to have "bug categories" is because
I'd want to treat those differently. But I'm not sure how just adding a
field would really allow me to do that.

>     - A deadline field (patch in hand and approved, awaiting checkin)

	Agreed, definitely. Or a way to associate dates with Target Milestones
-- that would be the best.

>     - The ability to easily create dependent or blocking bugs from one
>       bug -- this would make it a one-click deal to generate a child bug
>       to which we'd only need to enter a summary and description.

	I agree.

>     - A way to view a time-cut summary of comments posted to a `bug
>       subtree' so you can get an overview of all the activity done on
>       that bug 

	By "bug subtree" I assume that you mean "this bug and all its
dependencies?" This would probably be less useful than all the above
features, but would still be neat and helpful.

>     - I have entertained before an idea of a "parent bug" field that
>       would *not* be the same as blocks. I am still thinking this one
>       over.

	What would it indicate?

	Are there RFEs on b.m.o for any of these things?

	-Max
-- 
Maxwell Kanat-Alexander
2nd Level Tech Support Engineer, USA
Kerio Technologies, Inc.
2041 Mission College Blvd. Suite 100
Santa Clara, CA 95054
Phone: (408) 496-4500
Fax: (408) 496-6902
Web: http://www.kerio.com/support.html