Adding tracking states to Bugzilla

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

Adding tracking states to Bugzilla

Z. G. Fuestie
I maintain a customized version of Bugzilla at my organization.
Currently, some managers want me to add a new state to our Bugzilla.
It would mean the same as "ACCEPTED" but carry the additional meaning
that it's not actively being worked on.

I can handle the technical aspects of modifying Bugzilla to do this,
but the real question I have is should this be done at all?  I don't
think this is a good idea, (if people want something like
this it shouldn't be a state) but I was wondering what the people on
this list thought of adding this kind of state vs. some other device.

Any opinions or experiences would be greatly appreciated.
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists@...>
Reply | Threaded
Open this post in threaded view
|

Re: Adding tracking states to Bugzilla

Jochen Wiedmann
On Dec 4, 2007 11:09 AM, Z. G. Fuestie <[hidden email]> wrote:

> I can handle the technical aspects of modifying Bugzilla to do this,
> but the real question I have is should this be done at all?  I don't
> think this is a good idea, (if people want something like
> this it shouldn't be a state) but I was wondering what the people on
> this list thought of adding this kind of state vs. some other device.

We use keywords like "wait", or "wait_for_foo", to achieve the same goal.



--
Look, that's why there's rules, understand? So that you think before
you break 'em.

    -- (Terry Pratchett, Thief of Time)
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists@...>
Reply | Threaded
Open this post in threaded view
|

Re: Adding tracking states to Bugzilla

Frédéric Buclin
In reply to this post by Z. G. Fuestie
Z. G. Fuestie a écrit :
> I maintain a customized version of Bugzilla at my organization.
> Currently, some managers want me to add a new state to our Bugzilla.
> It would mean the same as "ACCEPTED" but carry the additional meaning
> that it's not actively being worked on.


Bugzilla 3.2 lets you add new bug statuses from the UI.
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists@...>
Reply | Threaded
Open this post in threaded view
|

Re: Adding tracking states to Bugzilla

Max Kanat-Alexander
In reply to this post by Z. G. Fuestie
On Tue, 4 Dec 2007 02:09:51 -0800 "Z. G. Fuestie"
<[hidden email]> wrote:
> I can handle the technical aspects of modifying Bugzilla to do this,
> but the real question I have is should this be done at all?  I don't
> think this is a good idea, (if people want something like
> this it shouldn't be a state) but I was wondering what the people on
> this list thought of adding this kind of state vs. some other device.

        We just keep bugs in NEW for that. There's no need for ASSIGNED
to mean "accepted"--it's obvious that the bug is accepted if it's
assigned to you and you didn't reassign it.

        That's also why we have "nobody" accounts on
bugzilla.mozilla.org--because *those* actually indicate nobody is
working on it, not some status.

        You know, we probably ought to just have a built-in mechanism
for "assigned to nobody" in Bugzilla, since we always seem to need it.

        -Max
--
http://www.everythingsolved.com/
Competent, Friendly Bugzilla and Perl Services. Everything Else, too.
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists@...>
Reply | Threaded
Open this post in threaded view
|

Re: Adding tracking states to Bugzilla

Tosh, Michael J
In reply to this post by Z. G. Fuestie
Sounds to me like you might benefit to use the UNCONFIRMED state if you
aren't already.

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Z. G.
Fuestie
Sent: Tuesday, December 04, 2007 5:10 AM
To: [hidden email]
Subject: Adding tracking states to Bugzilla

I maintain a customized version of Bugzilla at my organization.
Currently, some managers want me to add a new state to our Bugzilla.
It would mean the same as "ACCEPTED" but carry the additional meaning
that it's not actively being worked on.

I can handle the technical aspects of modifying Bugzilla to do this,
but the real question I have is should this be done at all?  I don't
think this is a good idea, (if people want something like
this it shouldn't be a state) but I was wondering what the people on
this list thought of adding this kind of state vs. some other device.

Any opinions or experiences would be greatly appreciated.
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=dev-apps-bugzilla@...
lla.org>
_______________________________________________
dev-apps-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-bugzilla
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists@...>
Reply | Threaded
Open this post in threaded view
|

Re: Adding tracking states to Bugzilla

Gregary Hendricks
In reply to this post by Z. G. Fuestie
On Tue, 2007-12-04 at 04:25 -0800, Max Kanat-Alexander wrote:

> On Tue, 4 Dec 2007 02:09:51 -0800 "Z. G. Fuestie"
> <[hidden email]> wrote:
> > I can handle the technical aspects of modifying Bugzilla to do this,
> > but the real question I have is should this be done at all?  I don't
> > think this is a good idea, (if people want something like
> > this it shouldn't be a state) but I was wondering what the people on
> > this list thought of adding this kind of state vs. some other device.
>
> We just keep bugs in NEW for that. There's no need for ASSIGNED
> to mean "accepted"--it's obvious that the bug is accepted if it's
> assigned to you and you didn't reassign it.
>

We do the same. If you are looking to differentiate bugs that have been
looked at vs those that are truly NEW, we use the priority. All new bugs
come in with a priority of P5 - None and once they are reviewed, are
moved to a P0 - P4. They are left in the NEW state however, until they
are being worked on, then they are ASSIGNED.

Greg


-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists@...>
Reply | Threaded
Open this post in threaded view
|

Re: Adding tracking states to Bugzilla

Gervase Markham
In reply to this post by Max Kanat-Alexander
Max Kanat-Alexander wrote:
> That's also why we have "nobody" accounts on
> bugzilla.mozilla.org--because *those* actually indicate nobody is
> working on it, not some status.

Indeed - although that is generally considered to be a hacky workaround
for the fact that it's not possible to assign a bug to _actual_ nobody.

Gerv
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists@...>