[Develop] added a needsinfo resolution in bugzilla

[Paul Widmer]

Sounds like a good idea.  I've seen this with a support database system at
one of my past jobs.  So there would be status' like "waiting for customer"
or "waiting for design".  So having something like you suggested seems like
a great idea.

But if you can automate the "ping" e-mail where you say, "just wanting to
see if you were able to get some more information to us so that we can
resolve this bug...".  I.e. if you request information from a bug submitter
then you can indicate that you want to ping them in 10 days.  That way you
don't have to search through the NEEDSINFO bugs to see which ones you need
to ping/change to INVALID.

-Cheers, Paul (pwiddy)


On Jan 6, 2008 5:29 PM, will <willg at bluesock.org> wrote:

> I had in my todo list a task to add a NEEDSINFO resolution to Bugzilla.
>  I added it just now.
>
> We can change it if it doesn't work out.  I don't recall offhand what
> the circumstances were that resulted me in adding it to my todo list.
>
> So the use case for the NEEDSINFO resolution is this:
>
> """
> User Bob creates a bug related to some problem he's having.  Developer
> Susan looks at the problem, but needs more information from Bob--say she
> needs a screenshot because the issue is ui-related.  Susan adds a
> comment to the bug along the lines of "Bob--can you attach a screenshot
> so that I can see what you're seeing?" and switches the resolution to
> NEEDSINFO.
> """
>
> This makes it much easier for us to query all the bugs that are in a
> NEEDSINFO state and push them along.  Bugs that haven't gotten new
> information after some time can get a friendly ping.  Bugs that haven't
> gotten new information after some time and a friendly ping can be moved
> to INVALID or WORKSFORME or something like that.
>
> This will help us keep bugs moving along and will reduce the number of
> zombie bugs that we've got sitting around ad infinitum.
>
> Any thoughts, suggestions, concerns, etc...  reply here.
>
> /will
> _______________________________________________
> Develop mailing list
> Develop at pculture.org
> http://participatoryculture.org/mailman/listinfo/develop
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://participatoryculture.org/pipermail/develop/attachments/20080110/49066064/attachment.html