The bug owner and the TFV seem to be basic info for any bug. I'd like to not have to click the link to get these values. There may be others that everyone can agree on... Thanks!

The problem here is getting a list of things everyone agrees on. I, for one, would not have put TFV in my list. It's pretty easy to figure out the bug owner by looking at who the mail is sent to.

Reassigning to dmose@mozilla.org, who now has front-line responsibility for all Bonsai and Bugzilla bugs.

Reassigning back to me. That stuff about me no longer being the front-line person responsible for Bugzilla and Bonsai turned out to be short-lived. Please pardon our confusion, and I'm very sorry about the spam.

Getting a list of things everyone agrees on would be hard to do... To solve this problem, how about making this a user-definable preference? That is, create a section where one can define which pieces of info like this should be mailed each time. Another possible consideration I see here: the goal from the user's standpoint is to save him time by not making him click on the link everytime... I am thinking, which option would be the best in terms of saving server CPU usage and network bandwidth?? I would imagine that putting in a system like the one suggested would require more CPU usage from the server, but (depending how how much info is e-mailed each time) it might also conserve network bandwidth... This is too tricky a question for me to think about... I only mention it because of the way the Mozilla CVS server is CPU-bound... Seems this problem is rather like the CVS -z compression option, where -z9 saves bandwidth at the expense of CPU power... There is always that "optimal threshold."

One piece of information which _would_ be useful, and which is not directly available by jumping to the bug, is who on earth modified the bug in the first place. IOW, who is responsible for causing the notification. At the moment, to get this info, you have to go to the bug (not a problem, I often do that anyway), and then click on "View Bug Activity", and then scroll to the bottom of the page.

This patch (to processmail r1.16+): *************** *** 297,302 **** --- 299,305 ---- close DIFFS; $substs{"neworchanged"} = $verb; $substs{"summary"} = $::bug{'short_desc'}; + $substs{"changedby"} = $nametoexclude; my $msg = PerformSubsts(Param("changedmail"), \%substs); if (!$regenerate) { should allow you to add something like "Changed by: %changedby%" to the "changedmail" param. Another useful addition to changedmail is a bug activity link such as: Bug activity: %urlbase%show_activity.cgi?id=%bugid%

As I think about it more and more, I think the idea of including info on who last changed the bug is a VERY good idea. I think the one-line patch included to do this looks like a nice clean way to do it, too. I say the addition of making it a link to the last entry in the View Bug Activity report should be done as well if this is to be done, however, since this would help establish the connection, showing where the info came from in the first place.

Who changed the bug is present in the new email system. Still no way of the user specifying what fields they always want for a bug report.

tara@tequilarista.org is the new owner of Bugzilla and Bonsai. (For details, see my posting in netscape.public.mozilla.webtools, news://news.mozilla.org/38F5D90D.F40E8C1A%40geocast.com .)

getting this on the radar. Now that we have email preferences this is possible.

*** Bug 71885 has been marked as a duplicate of this bug. ***

Consolidating all these reports ... *** This bug has been marked as a duplicate of 86201 ***

moving to Bugzilla product reassign to default owner/qa for INVALID/WONTFIX/WORKSFORME/DUPLICATE

moving to Bugzilla product reassign to default owner/qa for INVALID/WONTFIX/WORKSFORME/DUPLICATE

Verified duplicate