625194 - Set the QA contact for all bugs in the Bugzilla product to [e-mail]

Status: RESOLVED FIXED

(Developer Services :: General, task)

Description

[Frédéric Buclin]

See the URL. The tabular report shows that many bugs in the Bugzilla product have a QA contact which is not [e-mail] (fortunately, only for closed bugs). I don't know about bugbot and other Bugzilla devs, but I personally only watch the default QA contact to keep an eye on what's going on in this product, especially status and resolution changes. I fixed ~30 bugs manually, some pretty old, some others which have recently been retargetted to the Bugzilla product without resetting the default QA contact. But the remaining bugs in the tabular report are just too many, and I don't want to spam hundreds of users for something so minor. So my request is to fix them all at once from the MySQL command-line, so that this change doesn't affect delta_ts nor spam everybody. Just in case someone one day starts playing with a bug and nobody notices because the bug is out of our radar. (Consider this as being low priority.)

Comment 1

[David Lawrence [:dkl]]

justdave, is this something you can do against the live database?

Dave

Comment 2

[David Lawrence [:dkl]]

justdave, ping

Comment 3

[David Lawrence [:dkl]]

Can this be done now by watching the components instead? Do you still need this to be migrated?

dkl

Comment 4

[Frédéric Buclin]

(In reply to David Lawrence [:dkl] from comment #3)
> Do you still need this to be migrated?

Would still be good to do, yes, independently of the component watching.

Comment 5

[Frédéric Buclin]

Also, another good reason to do it is that the wrong people would be spammed. For instance, there are 141 bugs with reviewers@ as QA contact. We shouldn't spam this mailing-list if someone edits these bugs.

Comment 6

[David Lawrence [:dkl]]

Attachment: Patch to reset assignee/qacontact for specific product and component (v1)

Here is a script that could be used to move the Bugzilla qa contacts back to their default values. It can also be done for assignees as well as I made the script work either way. This is not particularly useful for Mozilla related products but we could use it to help out the Bugzilla product. Since it is pretty generic I am letting LpSolit take a look at it along with glob.

dkl

Comment 7

[Frédéric Buclin]

Comment on attachment 675919 [details] [diff] [review]
Patch to reset assignee/qacontact for specific product and component (v1)

Err... that's not what I want here. All I want is to SILENTLY change the QA contact, not spam everybody by updating delta_ts. If you update delta_ts but don't send emails, sanitycheck.cgi will complain and the next time someone clicks the "Send unsent emails" link, this is going to generate a lot of spam. What your script does can already be done in a mass-change. No need for this script. (Note that your script isn't safe anyway, because you forgot -T in the shebang, and so nothing is tainted.)


It's a trivial SQL command which I'm asking for:

UPDATE bugs SET qa_contact = (SELECT userid FROM profiles WHERE login_name = '[e-mail]') WHERE product_id = (SELECT id FROM products WHERE name = 'Bugzilla');

Comment 8

[David Lawrence [:dkl]]

(In reply to Frédéric Buclin from comment #7)
> Comment on attachment 675919 [details] [diff] [review]
> Patch to reset assignee/qacontact for specific product and component (v1)
> 
> Err... that's not what I want here. All I want is to SILENTLY change the QA
> contact, not spam everybody by updating delta_ts. If you update delta_ts but
> don't send emails, sanitycheck.cgi will complain and the next time someone
> clicks the "Send unsent emails" link, this is going to generate a lot of
> spam. What your script does can already be done in a mass-change. No need
> for this script. (Note that your script isn't safe anyway, because you
> forgot -T in the shebang, and so nothing is tainted.)

We do not run sanitycheck.cgi on a normal basis and therefore probably would not send the unsent emails.

But in the script, I also set lastdiffed which should keep the sanitycheck.cgi from complaining about the unsent emails for those affected by my script.

I will submit a new patch that uses -T for taint checking. Forgot to add that before.

> 
> It's a trivial SQL command which I'm asking for:
> 
> UPDATE bugs SET qa_contact = (SELECT userid FROM profiles WHERE login_name =
> '[e-mail]') WHERE product_id = (SELECT id FROM products
> WHERE name = 'Bugzilla');

Doing just this statement doesn't properly update bugs_activity with the user changes which is why the script was needed.

dkl

Comment 9

[Frédéric Buclin]

(In reply to David Lawrence [:dkl] from comment #8)
> Doing just this statement doesn't properly update bugs_activity with the
> user changes which is why the script was needed.

That's exactly what I'm asking for! :)

Comment 10

[David Lawrence [:dkl]]

Attachment: Patch to reset assignee/qacontact for specific product and component (v2)

Comment 11

[Frédéric Buclin]

Comment on attachment 676672 [details] [diff] [review]
Patch to reset assignee/qacontact for specific product and component (v2)

This is a bmo only script, so I will let glob review it. It goes way further than what I was asking for.

Comment 12

[David Lawrence [:dkl]]

(In reply to Frédéric Buclin from comment #9)
> (In reply to David Lawrence [:dkl] from comment #8)
> > Doing just this statement doesn't properly update bugs_activity with the
> > user changes which is why the script was needed.
> 
> That's exactly what I'm asking for! :)

I would not be happy to make this change to the bug attributes without recording the change in the bugs activity table properly. There is a change in the activity for when the qa contact was changed to the non-default, user why shouldn't there be an entry for when the script changes it back. I would rather not purposely introduce this kind of inconsistency. So the script keeps that from occurring.

dkl

Comment 13

[:glob ✱]

Comment on attachment 676672 [details] [diff] [review]
Patch to reset assignee/qacontact for specific product and component (v2)

Review of attachment 676672 [details] [diff] [review]:
-----------------------------------------------------------------

r=glob, with the issues noted to be fixed on commit.

nit: this file contains trailing spaces, please remove.

::: contrib/reorg-tools/reset_default_user.pl
@@ +51,5 @@
> +}
> +
> +# We will need these for entering into bugs_activity
> +my $who   = Bugzilla::User->new({ name => '[e-mail]' });
> +my $field = Bugzilla::Field->new({ name => $field_name });

you need to validate that $field_name is either assigned_to or qa_contact.
currently the script will accept any valid field, but then later on silently morph it to assigned_to (in most cases).

@@ +133,5 @@
> +                 undef, $bug_id, $who->id, $timestamp, $field->id, $old_user->login, $new_user->login);
> +        $dbh->do("UPDATE bugs SET delta_ts = ?, lastdiffed = ? WHERE bug_id = ?", 
> +                 undef, $timestamp, $timestamp, $bug_id);
> +
> +        print "done.\n";

you need a transaction block for these statements.

Comment 14

[David Lawrence [:dkl]]

Thanks

(In reply to Byron Jones ‹:glob› from comment #13)
> > +# We will need these for entering into bugs_activity
> > +my $who   = Bugzilla::User->new({ name => '[e-mail]' });
> > +my $field = Bugzilla::Field->new({ name => $field_name });
> 
> you need to validate that $field_name is either assigned_to or qa_contact.
> currently the script will accept any valid field, but then later on silently
> morph it to assigned_to (in most cases).

I do that earlier before those statements:

+if (!$product || $help
+    || ($field_name ne 'assigned_to' && $field_name ne 'qa_contact')) 
+{
+    usage();
+    exit(1);
+}

> you need a transaction block for these statements.

done

Committing to: bzr+ssh://[e-mail]/bmo/4.0 
added contrib/reorg-tools/reset_default_user.pl
Committed revision 8379.

Committing to: bzr+ssh://[e-mail]/bmo/4.2 
added contrib/reorg-tools/reset_default_user.pl
Committed revision 8402.

Comment 15

[David Lawrence [:dkl]]

LpSolit. Are you ready to go for us to reset the qa contact on Bugzilla product bugs? I can go ahead and move this bug over to IT for them to do that changes to production. Including closed bugs, this script will update 5000+ bugs (no email sent). Or do you only want the open bugs the be updated?

Steps:

# cd /path/to/bugzilla/code
# perl -wT -I. contrib/reorg-tools/reset_default_user.pl --field qa_contact --product Bugzilla

dkl

Comment 16

[Frédéric Buclin]

(In reply to David Lawrence [:dkl] from comment #15)
> LpSolit. Are you ready to go for us to reset the qa contact on Bugzilla
> product bugs?

Yes, let's do it. Also for closed bugs.

Comment 17

[David Lawrence [:dkl]]

(In reply to Frédéric Buclin from comment #16)
> (In reply to David Lawrence [:dkl] from comment #15)
> > LpSolit. Are you ready to go for us to reset the qa contact on Bugzilla
> > product bugs?
> 
> Yes, let's do it. Also for closed bugs.

Cool. Will do it now then.

Admin, please execute the following steps on a BMO web head of your choice:

# cd /path/to/bugzilla/code
# perl -wT -I. contrib/reorg-tools/reset_default_user.pl --field qa_contact --product Bugzilla

Thanks
dkl

Comment 18

[Shyam Mani [:fox2mike]]

Attachment: Command output

Done.

Comment 19

[Shyam Mani [:fox2mike]]

Sorry for the delay!