bug status

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

bug status

Kelly Holt

I’ve set-up a 2.20 version of Bugzilla to test and try out.

 

I’ve noticed that there is not a place or status for bugs to enter for needed information from the reporter or anyone else in the users-list.

 

Is there a way to create a new state and have the default files allow for a ‘NEW’ or ‘ASSIGNED’ bug to enter a ‘NEEDINFO’ state? And then a ‘INFOGIVEN’ after?

 

Any help on this is appreciated.

 

Regards,

Kelly Holt


_______________________________________________
support-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/support-bugzilla
Reply | Threaded
Open this post in threaded view
|

RE: bug status

Jay Glanville
Hello Kelly,

We've just recently upgraded from 2.18.3 to 2.20, so my knowledge of
2.20 is not quite absolute yet.

I don't know if 2.20 introduced functionality to address your issue.  If
it did, we'd very much like to use it.

However, if 2.20 doesn't add the functionality, you could try the
following.  The Target Milestone field contains the information of "when
we should try to address this issue".  However, if an issue requires
more information, and therefore one can't determine when it should be
addressed, you could target the bug for "Needs More Info".

So, to implement this idea, add a new Target Milestone for the product
named "NEEDS_INFO", plus leave the "---" target in the list.  Thus, if
management needs more information for the bug, then they could target it
for NEEDS_INFO.  When the developers have added the necessary
information, they would retarget it for "---".  This would tell
management that it's back to them for targeting.

Now, I don't know how well this would work, as I haven't tried it
myself.  It really depends on your team's work cycle.

JDG

PS: I've noticed that the PRIORITY and SEVERITY fields are modifiable
now.  So an alternative might be to add the NEEDS_INFO to the PRIORITY
field (ie: "we can't prioritize it until we get more information ...")


________________________________

        From: [hidden email]
[mailto:[hidden email]] On Behalf Of Kelly
Holt
        Sent: Thursday, January 12, 2006 6:16 PM
        To: [hidden email]
        Subject: bug status
       
       

        I've set-up a 2.20 version of Bugzilla to test and try out.

         

        I've noticed that there is not a place or status for bugs to
enter for needed information from the reporter or anyone else in the
users-list.

         

        Is there a way to create a new state and have the default files
allow for a 'NEW' or 'ASSIGNED' bug to enter a 'NEEDINFO' state? And
then a 'INFOGIVEN' after?

         

        Any help on this is appreciated.

         

        Regards,

        Kelly Holt

_______________________________________________
support-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/support-bugzilla
Reply | Threaded
Open this post in threaded view
|

Re: bug status

Michael Bellomo
In reply to this post by Kelly Holt
What we do here for that case is mark the bug as fixed / invalid.  If the bug doesn't have enough information for the developers to know what's wrong, we consider that invalid.  We debated this for a while and were going to use the milestone like Jay suggested, but ended up deciding that people need to learn how to write good bugs...so we consider those invalid.

Another option would be just to add a comment to the bug:  need more info please.  And that'll notify the reporter (assuming they have their preference set to get that mail).

    -Michael

Kelly Holt wrote:

I’ve set-up a 2.20 version of Bugzilla to test and try out.

 

I’ve noticed that there is not a place or status for bugs to enter for needed information from the reporter or anyone else in the users-list.

 

Is there a way to create a new state and have the default files allow for a ‘NEW’ or ‘ASSIGNED’ bug to enter a ‘NEEDINFO’ state? And then a ‘INFOGIVEN’ after?

 

Any help on this is appreciated.

 

Regards,

Kelly Holt


_______________________________________________ support-bugzilla mailing list [hidden email] https://lists.mozilla.org/listinfo/support-bugzilla

_______________________________________________
support-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/support-bugzilla
Reply | Threaded
Open this post in threaded view
|

RE: bug status

Darrell Fluet
In reply to this post by Kelly Holt

We had a similar issue in trying to keep track of ‘who’s court the ball was in’ regarding questions to and responses from clients. What we did was simply add another resolution called ‘WaitingResponse’ under the Fixed status.  It’s not perfect but it allows you to easily track the information flow and do searches to find any issues that are currently ‘waiting for a response’ from the client.

 

Darrell Fluet

 

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Kelly Holt
Sent:
January 12, 2006 4:16 PM
To: [hidden email]
Subject: bug status

 

I’ve set-up a 2.20 version of Bugzilla to test and try out.

 

I’ve noticed that there is not a place or status for bugs to enter for needed information from the reporter or anyone else in the users-list.

 

Is there a way to create a new state and have the default files allow for a ‘NEW’ or ‘ASSIGNED’ bug to enter a ‘NEEDINFO’ state? And then a ‘INFOGIVEN’ after?

 

Any help on this is appreciated.

 

Regards,

Kelly Holt


_______________________________________________
support-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/support-bugzilla
Reply | Threaded
Open this post in threaded view
|

RE: bug status

Jeff Jensen
If you don't want to change Bugzilla, use a flag for these kinds of things.


Quoting Darrell Fluet <[hidden email]>:

> We had a similar issue in trying to keep track of 'who's court the ball was
> in' regarding questions to and responses from clients. What we did was
> simply add another resolution called 'WaitingResponse' under the Fixed
> status.  It's not perfect but it allows you to easily track the information
> flow and do searches to find any issues that are currently 'waiting for a
> response' from the client.
>
>
>
> Darrell Fluet
>
>
>
> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of Kelly Holt
> Sent: January 12, 2006 4:16 PM
> To: [hidden email]
> Subject: bug status
>
>
>
> I've set-up a 2.20 version of Bugzilla to test and try out.
>
>
>
> I've noticed that there is not a place or status for bugs to enter for
> needed information from the reporter or anyone else in the users-list.
>
>
>
> Is there a way to create a new state and have the default files allow for a
> 'NEW' or 'ASSIGNED' bug to enter a 'NEEDINFO' state? And then a 'INFOGIVEN'
> after?
>
>
>
> Any help on this is appreciated.
>
>
>
> Regards,
>
> Kelly Holt
>
>



_______________________________________________
support-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/support-bugzilla
Reply | Threaded
Open this post in threaded view
|

RE: bug status

Jay Glanville
In reply to this post by Kelly Holt
Actually, another thought occurred to me.  If your bug raisers are
external, you could configure bugzilla so that the starting status of a
bug is UNCONFIRMED.  Then, you only confirm them (by moving them to NEW)
once all the necessary information has been provided.

JDG

> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf
> Of Jay Glanville
> Sent: Thursday, January 12, 2006 9:17 PM
> To: Kelly Holt; [hidden email]
> Subject: RE: bug status
>
> Hello Kelly,
>
> We've just recently upgraded from 2.18.3 to 2.20, so my knowledge of
> 2.20 is not quite absolute yet.
>
> I don't know if 2.20 introduced functionality to address your
> issue.  If
> it did, we'd very much like to use it.
>
> However, if 2.20 doesn't add the functionality, you could try the
> following.  The Target Milestone field contains the
> information of "when
> we should try to address this issue".  However, if an issue requires
> more information, and therefore one can't determine when it should be
> addressed, you could target the bug for "Needs More Info".
>
> So, to implement this idea, add a new Target Milestone for the product
> named "NEEDS_INFO", plus leave the "---" target in the list.  Thus, if
> management needs more information for the bug, then they
> could target it
> for NEEDS_INFO.  When the developers have added the necessary
> information, they would retarget it for "---".  This would tell
> management that it's back to them for targeting.
>
> Now, I don't know how well this would work, as I haven't tried it
> myself.  It really depends on your team's work cycle.
>
> JDG
>
> PS: I've noticed that the PRIORITY and SEVERITY fields are modifiable
> now.  So an alternative might be to add the NEEDS_INFO to the PRIORITY
> field (ie: "we can't prioritize it until we get more information ...")
>
>
> ________________________________
>
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of Kelly
> Holt
> Sent: Thursday, January 12, 2006 6:16 PM
> To: [hidden email]
> Subject: bug status
>
>
>
> I've set-up a 2.20 version of Bugzilla to test and try out.
>
>
>
> I've noticed that there is not a place or status for bugs to
> enter for needed information from the reporter or anyone else in the
> users-list.
>
>
>
> Is there a way to create a new state and have the default files
> allow for a 'NEW' or 'ASSIGNED' bug to enter a 'NEEDINFO' state? And
> then a 'INFOGIVEN' after?
>
>
>
> Any help on this is appreciated.
>
>
>
> Regards,
>
> Kelly Holt
>
> _______________________________________________
> support-bugzilla mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/support-bugzilla
>
_______________________________________________
support-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/support-bugzilla
Reply | Threaded
Open this post in threaded view
|

RE: bug status

Kelly Holt
In reply to this post by Kelly Holt
To: Kelly Holt; [hidden email]
Subject: RE: bug status

Actually, another thought occurred to me.  If your bug raisers are
external, you could configure bugzilla so that the starting status of a
bug is UNCONFIRMED.  Then, you only confirm them (by moving them to NEW)
once all the necessary information has been provided.

JDG
==================
Thanks Jay, I got it.

Kelly
_______________________________________________
support-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/support-bugzilla