Bugzilla Bug-Tagging process

Hi,

does anyone know if "normal" Bugzilla users at B.K.O are able to mark a bug as
VERIFIED?

It would help a lot reducing all those open bugreports.

At our company we handle bugzilla like this:

1. A bug is opened by either a developer or a member of the QA team.
2. Bug gets fixed, developer marks it as RESOLVED (FIXED).
3. A member of the QA team retests all of his bugs and marks every bug as
VERIFIED (FIXED), if the bug has really been fixed, otherwise it gets re-
opened again.

This way you get rid of open bugs quickly, and you don't have to ask all the
time if the bug has really been fixed (normally you know that you have done it
anyway :-)).

Right now it is quite annoying asking all the time if the bug is fixed,
especially on old bugreports where nobody is answering anymore.

Andi
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

Do you read this entry :

http://quality.kde.org/develop/howto/howtobugs.php

For normal users, i don't know exactly. I agree with you, this will
more simple for the team.

Gilles



2010/7/11 Andi Clemens <[hidden email]>:

> Hi,
>
> does anyone know if "normal" Bugzilla users at B.K.O are able to mark a bug as
> VERIFIED?
>
> It would help a lot reducing all those open bugreports.
>
> At our company we handle bugzilla like this:
>
> 1. A bug is opened by either a developer or a member of the QA team.
> 2. Bug gets fixed, developer marks it as RESOLVED (FIXED).
> 3. A member of the QA team retests all of his bugs and marks every bug as
> VERIFIED (FIXED), if the bug has really been fixed, otherwise it gets re-
> opened again.
>
> This way you get rid of open bugs quickly, and you don't have to ask all the
> time if the bug has really been fixed (normally you know that you have done it
> anyway :-)).
>
> Right now it is quite annoying asking all the time if the bug is fixed,
> especially on old bugreports where nobody is answering anymore.
>
> Andi
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Martin Klapetek]

With bugs, that were reported by me and are closed, I am able to set it to VERIFIED (as well as RESOLVED, REOPENED, CLOSED) and I suppose I am a 'normal user', but this privilleges have probably only reporters of the bugs (and of course asignees and admins).

Marty

On Sun, Jul 11, 2010 at 11:26, Andi Clemens <[hidden email]> wrote:

Hi,

does anyone know if "normal" Bugzilla users at B.K.O are able to mark a bug as
VERIFIED?

It would help a lot reducing all those open bugreports.

At our company we handle bugzilla like this:

1. A bug is opened by either a developer or a member of the QA team.
2. Bug gets fixed, developer marks it as RESOLVED (FIXED).
3. A member of the QA team retests all of his bugs and marks every bug as
VERIFIED (FIXED), if the bug has really been fixed, otherwise it gets re-
opened again.

This way you get rid of open bugs quickly, and you don't have to ask all the
time if the bug has really been fixed (normally you know that you have done it
anyway :-)).

Right now it is quite annoying asking all the time if the bug is fixed,
especially on old bugreports where nobody is answering anymore.

Andi
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Well this would be enough I guess, the one who reported a bug normally knows
best what didn't work for him, so if he can set a VERIFIED status, this would
be fine I guess.

Andi Clemens
-----------------
www.digikam.org

On Sunday 11 July 2010 12:12:13 Martin Klapetek wrote:

> With bugs, that were reported by me and are closed, I am able to set it to
> VERIFIED (as well as RESOLVED, REOPENED, CLOSED) and I suppose I am a
> 'normal user', but this privilleges have probably only reporters of the
> bugs (and of course asignees and admins).
>
> Marty
>
> On Sun, Jul 11, 2010 at 11:26, Andi Clemens <[hidden email]> wrote:
> > Hi,
> >
> > does anyone know if "normal" Bugzilla users at B.K.O are able to mark a
> > bug as
> > VERIFIED?
> >
> > It would help a lot reducing all those open bugreports.
> >
> > At our company we handle bugzilla like this:
> >
> > 1. A bug is opened by either a developer or a member of the QA team.
> > 2. Bug gets fixed, developer marks it as RESOLVED (FIXED).
> > 3. A member of the QA team retests all of his bugs and marks every bug as
> > VERIFIED (FIXED), if the bug has really been fixed, otherwise it gets re-
> > opened again.
> >
> > This way you get rid of open bugs quickly, and you don't have to ask all
> > the
> > time if the bug has really been fixed (normally you know that you have
> > done it
> > anyway :-)).
> >
> > Right now it is quite annoying asking all the time if the bug is fixed,
> > especially on old bugreports where nobody is answering anymore.
> >
> > Andi
> > _______________________________________________
> > Digikam-devel mailing list
> > [hidden email]
> > https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel