Re: Automatically set bugs to CLESED when verified - Mozilla

This is a discussion on Re: Automatically set bugs to CLESED when verified - Mozilla ; What is the difference between verified and closed. Or maybe what should the difference be interpreted to mean? On 2/8/06, Toepfer Philipp wrote: > > > Hello, > > today I received a proposal from our testing department to "merge" ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Re: Automatically set bugs to CLESED when verified

  1. Re: Automatically set bugs to CLESED when verified

    What is the difference between verified and closed. Or maybe what
    should the difference be interpreted to mean?

    On 2/8/06, Toepfer Philipp wrote:
    >
    >
    > Hello,
    >
    > today I received a proposal from our testing department to "merge" the
    > "VERIFIED" and the "CLOSED" steps in bugzilla.
    > The aim is to set the bugs automatically as "CLOSED" as soon as they are
    > marked as "VERIFIED".
    > Is this possible?
    >
    > Regards
    >
    >
    > Philipp Töpfer
    > System Architekt
    >
    > Magneti Marelli
    > Elektronische Systeme GmbH
    > Industriestr. 3
    > 70565 Stuttgart
    >
    > Tel +49 (0) 711 1237 1134
    > Fax +49 (0) 711 1237 1199
    > _______________________________________________
    > support-bugzilla mailing list
    > support-bugzilla@lists.mozilla.org
    > https://lists.mozilla.org/listinfo/support-bugzilla
    >
    >
    >



    --
    --dfc
    douglasfcalvert@gmail.com

  2. Re: Automatically set bugs to CLESED when verified

    Douglas F. Calvert wrote:
    > What is the difference between verified and closed. Or maybe what
    > should the difference be interpreted to mean?


    This depends entirely on your processes. For instance, we don't even
    use the VERIFIED and CLOSED states.

    In *some* organizations, there is a process where development FIXES
    bugs, QA VERIFIES them, and when the product version is finally shipped
    to the customer, the bug is CLOSED. This is so that the support team can
    keep track of which bugs have fixes available in the field, and when.

    But all of this depends on your processes. You have to decide what your
    process flow is, and then map the flow to Bugzilla's states. (It's OK to
    adjust your processes to fit what's actually available in Bugzilla, or
    to adjust Bugzilla to fit your processes, as your comfort level dictates).

+ Reply to Thread