On Thu, 2006-03-09 at 11:01 -0500, Gary Oberbrunner wrote: > Célio Cidral Junior wrote: > > 2006/3/9, Matthew Good <[EMAIL PROTECTED]>: > >> there's little distinction between "priority" and "severity". > > > > After thinking again about priority vs. severity, I agree with you. > > These concepts are so related so that there's no reason to have them > > separated. > > Not to restart an old discussion, but they seem quite different to me. > Severity is customer-facing, i.e. how severe the impact is to them. Priority > is inward-facing, i.e. how important it is to fix. Maybe the customer with > the severe impact is not an important customer, or the customer doesn't think > it's severe but for other reasons we really need to get it fixed. > > For project tracking and planning purposes, priority is the most important, > but especially if you're going to let customers see into your trac, severity > can be important to them.
Well, that's why there are custom fields. Different people have different needs for the ticket fields they need to track. For a lot of projects having type/priority/severity is redundant and confusing, so I don't think it's a good "default" field. If you need additional fields go ahead and make use of the custom fields to tweak Trac to your business needs. -- Matthew Good <[EMAIL PROTECTED]> _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
