271577 - VotesToConfirm functionality lies about who confirmed the bug

Status: RESOLVED DUPLICATE of bug 271474

(Bugzilla :: Creating/Changing Bugs, defect)

Description

[Boris Zbarsky [:bzbarsky]]

STEPS TO REPRODUCE:

1)  Lower threshold for votes to confirm on bugzilla.mozilla.org
2)  Receive a bunch of "confirmed by popular vote" bugmail
3)  Look at a bug that got confirmed in this way

ACTUAL RESULTS:  There is a comment from some random bugzilla user saying the
bug is confirmed by popular vote.

EXPECTED RESULTS:  The bug display makes it clear that it's Bugzilla itself
which confirmed the bug instead of misattributing this change to some poor
schmuck who just voted for it.

This is a pretty serious bug, in my opinion, because it makes it look like a
user made a comment when the user did not, in fact, do so.

Comment 1

[Dave Miller [:justdave]]

hmm, well, it *was* that person's vote that put it over. :)

But yes, voting is designed to not draw immediate attention to the person doing
the voting I suppose, so I guess that is a bit presumptive.

There is no "system user" for Bugzilla to attribute it, however.  How would you
suggest it be handled?  The assignee and so forth *do* need to get notified that
the status changed somehow...

Comment 2

[Boris Zbarsky [:bzbarsky]]

I don't have suggestions for how this is to be handled, offhand.  I just know
that several people got flamed for confirming bugs that obviosly should not have
been confirmed, and that said people had no idea the bugs had even gotten
confirmed....

Comment 3

[Dave Miller [:justdave]]

This has been this way for as long as we've had the UNCONFIRMED status, so it's
not a regression, and therefor is not blocking the release.  But it's still an
annoyance and doesn't mean we shouldn't fix it.

Comment 4

[Vlad Dascalu]

This got/will be fixed in bug 271474 by the patch that solves the SQL error as well.

We solved this by making the admin appear in the change log. He's the only one
that performes an action at the recorded timestamp :-)

*** This bug has been marked as a duplicate of 271474 ***