2009/11/27 PulkoMandy <pulkomandy@xxxxxxxxx>: > 2009/11/27 Niels Reedijk <niels.reedijk@xxxxxxxxx>: >> 2009/11/27 PulkoMandy <pulkomandy@xxxxxxxxx>: >>>> Anyway, that would only work with the new workflow where there is a >>>> difference between 'new' and 'assigned' (or CONFIRMED in bugzilla >>>> language). >>> >>> The difference is actually already there, only it's between new && >>> ower = nobody and new && owner = some dev. The latter IS the >>> "assigned" state. >> >> That would theoretically be correct, but right now we have default >> component owners (and there is no compelling reason to change that), >> so if a ticket is created in a component that already has an owner, >> then you cannot distinguish it from a ticket that is 'assigned' to >> someone. >> >> N> > > This is on purpose : if you know where the problem is, you select a > category and the ticket is automatically assigned to the right person, > so the sorter guy don't have to worry about it. If the categorization > is wrong, it's not a big problem, the selected dev can either reassign > the ticket to someone else, or reassign it to "nobody" to signal it > needs to be assigned. I think the first case would be more common, as > devs usually know their way around at least related part of the > system... Right, and instead I think that if we manage to set up a triaging team, dev's won't have to spend time chasing incomplete bug reports even when they are assigned to their component. Nothing prohibits a dev from picking up a bug report when it is 'new', but if it is a bad one, he can leave it at new and a triager will pick it up and make it into a good one. That's the way I see things happening and for that the current logic of the ticket workflow is insufficient. N>