101
edits
Changes
m
Noted update to Flowchart B, discussed IN-PROGRESS idea/timeout warning
See mconnor's [http://steelgryphon.com/blog/?page_id=61 A Modest Proposal] post
See also wiki (older) [[http://wiki.mozilla.org/index.php?title=BugzillaWorkflowImprovements:FlowChart_B&oldid=21478 FlowChart B|FlowChart B]] illustrating how these might fit together. ([[User:Gekacheka|Gekacheka]] 07:34, 1 Oct 2005 (PDT))
Here's the latest version of [http://steelgryphon.com/testcases/bugzilla-workflow-9.png Mike Connor's flowchart].
Latest [[BugzillaWorkflowImprovements:FlowChart B|FlowChart B]] added NEEDSINFO and Resolved DEFICIENT (and removed shortcut paths for simplicity). ([[User:Gekacheka|Gekacheka]] 18:25, 7 April 2007 (PDT))
=Other ideas=
: That's what READY is for, I think, no? [[User:Mconnor|Mconnor]]
:: I think IN-PROGRESS might be a better name for what you describe. Some developers accept a bug but have so many other tasks that they don't work on it for months, and it might progress faster if some other interested developer picked it up. Maybe for assigned/in-progress bugs bugzilla could issue a warning after 30days requesting a progress report (or expected date when work will start). And/or IN-PROGRESS could expire after some period of no activity. ([[User:Gekacheka|Gekacheka]] 18:25, 7 April 2007 (PDT))
