Closed Bug 821070 Opened 12 years ago Closed 11 years ago

bugmail sent by sanitycheck shows the wrong user as the changer

Categories

(Bugzilla :: Administration, task)

4.0.9
task
Not set
normal

Tracking

()

RESOLVED FIXED
Bugzilla 4.4

People

(Reporter: glob, Assigned: mail)

References

Details

(Whiteboard: [blocker will fix])

bugmail sent by sanitycheck shows the wrong user as the changer. i triggered sanitycheck -> send unsent bugmail the bugmail sent showed that i was the person who made the change: > X-Bugzilla-Who: glob@mozilla.com > > https://bugzilla.mozilla.org/show_bug.cgi?id=707617 > Byron Jones ‹:glob› <glob@mozilla.com> changed: > Status|RESOLVED |VERIFIED however this change was actually made by fox2mike
Assignee: nobody → glob
Blocks: bmo4.2
evidently this is the best we can do: # We cannot simply look at the bugs_activity table to find who did the # last change in a given bug, as e.g. adding a comment doesn't add any # entry to this table. And some other changes may be private # (such as time-related changes or private attachments or comments) # and so choosing this user as being the last one having done a change # for the bug may be problematic. So the best we can do at this point # is to choose the currently logged in user for email notification.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Inline history manages to figure it out somehow. I think the problem is the send_unsent tries to send one collective email for all changes since the last time mail was sent (which as mentioned, could have been done by more than one person). It should instead step the last_sent date forward for each collection of changes it can find that have the same changer and timestamp, and send a new email for each chunk.
Assignee: glob → administration
Status: RESOLVED → REOPENED
Component: General → Administration
OS: Mac OS X → All
Product: bugzilla.mozilla.org → Bugzilla
QA Contact: default-qa
Hardware: x86 → All
Resolution: INVALID → ---
Version: Production → 4.0.9
I suspect this could be fixed by bug 946565.
Status: REOPENED → NEW
Depends on: 946565
(In reply to Frédéric Buclin from comment #3) > I suspect this could be fixed by bug 946565. That would be correct. I was using sentunsentemail.pl when picking up this problem. -- simon
Status: NEW → RESOLVED
Closed: 12 years ago11 years ago
No longer depends on: 946565
Resolution: --- → DUPLICATE
This is not exactly a duplicate, though the root cause is the same. The other bug is about mixing changers while this bug is about running sanitycheck.cgi and having the admin being taken as the changer despite he didn't change anything. (and technically, your bug is newer than this one, so the dupe link should be reversed.)
Assignee: administration → sgreen
Status: RESOLVED → REOPENED
Depends on: 946565
Resolution: DUPLICATE → ---
Whiteboard: [blocker will fix]
Target Milestone: --- → Bugzilla 4.4
Blocker is now committed to trunk and 4.4. -- simon
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.