Status: Resolved Later

[Christopher Hicks]

On Thu, 9 Dec 2004, Kevin Benton wrote:

> That's a very good point.  As a person who is also responsible for 
> tracking process flow, I don't want to impact the priority / severity 
> levels just because something is pending.

That makes sense.

> A number of different pending statuses come to mind, but all of them 
> revolve around the developer waiting for action outside their control as 
> it relates directly to the bug in question.

What about using keywords?  We do that for bugs where somebody needs to be 
contacted.  I have a "contact" query that I do in the morning and run down 
the list of the folks that need to be contacted.  I stick the number in 
the whiteboard so I can print it easily and carry it with me if I'm going 
on the road and I'm going to be sitting long enough to call people at some 
point in that processs.

>> Why does pending need to be its own status?
>
> See above.  For status tracking, having a status of pending helps developers
> focus on what's hot at the moment.  It also helps managers look more closely
> at how the manager's developers are utilizing their time.

I think you could do the same think with keywords without having to modify 
bugzilla to make it work.

-- 
</chris>

"Fans of Mozilla's free, open-source Firefox browser make the
ardent Apple faithful look like a bunch of slackers."
- Rebecca Lieb at clickz.com