Changes to ticket summary should mirror those produced by Trac notification system

[Ryan J Ollos]

With the recently revived initiative to integrate parts of the AnnouncerPlugin into the Trac core, I've been trying to pay attention to the subtle ways in which the current Trac notification emails might differ from the AnnouncerPlugin notification emails.

Here is an email from the Trac notification system (subject of email was Re: [The Trac Project] #10953: Active mainnav navigation entry is not highlighted when running tracd (was: Active navigation entry is not highlighted when running tracd)).

Note that a change to the summary results in the addition of a (was: <old summary>) to the subject. That is nice, but I find the empty body of the email troubling. Compare that to an AnnouncerPlugin notification email that has Summary changes from <old> to <new> in the body of the message. I tend to think we should indicate the change in the subject and in the body of the message as well as the email subject.

#10953: Active mainnav navigation entry is not highlighted when running tracd
-------------------------------------------+------------------
 Reporter:  Ryan J Ollos <ryan.j.ollos@…>  |       Owner:
     Type:  defect                         |      Status:  new
 Priority:  normal                         |   Milestone:
Component:  general                        |     Version:
 Severity:  normal                         |  Resolution:
 Keywords:                                 |
-------------------------------------------+------------------
Release Notes:



API Changes:


-------------------------------------------+------------------

--
Ticket URL: <http://trac.edgewall.org/ticket/10953#comment:10>
The Trac Project <http://trac.edgewall.org/> The Trac Project