Re: [Aardvark Bugs 0000115]: Email notifications do not report whatwas updated

[Don Cragun <dcragun@xxxxxxxxx>]

Mark Brown wrote:
> The Bug says:
> > Summary:          Email notifications do not report what was updated
> > Description: 
> > The automatic email notifications that are sent to the Austin group list
> > for issue updates include the entire issue description and all notes, but
> > do not report what was updated.  There is a link in the email, and it is
> > possible to follow the link, scroll down to the issue history, and look for
> > the actions with today's date.  For example it might show that the field
> > "Organization" was changed to "Self".  However it would be nice if that was
> > reported in the email.
> > Desired Action: 
> > Change the email notification to report what was updated.  Preferably the
> > description and notes would not be included except when added or updated.
> The default for the tool was to present the information that you are seeing
> now PLUS a "history" statement at the end. I removed the history statement
> because I felt things were going to get too long. But there is a good point
> here in that the history statement really tells you exactly what has changed.
>
> I'll try to see what I can do here.
>
> -------------------
> Mark Brown/Austin/IBM
Hi Mark,
I know I'm dreaming here, but what I would really like to see in the 
update e-mails is the following:
1.  A link to the bug in Mantis: So I can quickly skip to the full bug
    report if I want to look at the whole thing.
2.  Summary: This field is short and gives me a brief idea of the
    subject matter
3.  Issue History: only the final entries that have the Date Modified
    value corresponding to the change that generated this e-mail.
4.  Project, Category, Type, Severity, Priority, & Status: iff the field
    isn't in the Issue History.  Issue ID is not needed since it is
    obvious from the link to the bug in Mantis.
5.  Date Submitted: so I have an idea of how long the bug has been
    around.  Last Modified is not needed since the time stamp on the
    Issue History entry tells me what I need to know here.
6.  The contents of any new or changed fields, but only if the change is
    not already visible in the Issue History.

I'm not sure about the Description and Desired Action fields.  They give
a lot of context, but they can be huge.  (#6 above obviously overrides
this if either of these fields changes.)

Cheers,
Don