Bugzilla semantics: marking bugs as triaged

[Allen Kistler]

Adam Williamson wrote:
> 
> [snip]
> 
> We were thinking about the NEW / ASSIGNED dichotomy, and Andy and I came
> to the conclusion that it doesn't really make a lot of sense.
> 
> [snip]
> 
> We sort of came to the conclusion that it'd probably make the most sense
> to have a 'Triaged' keyword that's used to affirm that a bug's been
> triaged (in fact there already is one, but it's not officially used in
> our current process), and abandon the distinction between NEW and
> ASSIGNED. Ideally, the ASSIGNED state would just be removed, but we
> could keep it and just note in our workflow / policy that it's not
> really used to mean anything in particular.
> 
> This could, I think, be implemented quite quickly if desired; I think we
> could rig something up to set all bugs in ASSIGNED state (except
> anaconda ones) to have the 'Triaged' keyword, that shouldn't be
> impossible.
> 
> We'd be interested in thoughts - negative, positive, whatever - on the
> idea. Thanks!


I believe the way Bugzilla works now, ASSIGNED = "Actively being worked" 
("Open Issues: In Progress Reported by You.  You reported the bug, the 
developer accepted the bug and is hopefully working on it.").  At least, 
it's supposed to be that way.  "My Front Page" recently changed and no 
longer shows Open bugs I've reported, but I believe that's a gaping bug 
in the new My Front Page implementation.  (Bugzilla on Bugzilla in 
progress...)