Changes between Version 1 and Version 2 of Ticket #10699


Ignore:
Timestamp:
Dec 12, 2012, 10:48:18 AM (11 years ago)
Author:
Ryan J Ollos
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #10699 – Description

    v1 v2  
    11With 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.
    22
    3 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)`).
     3Here is the subject of an email from the Trac notification system in which the summary was changed, with the body of the mail shown below.
     4{{{
     5#!email
     6Re: [The Trac Project] #10953: Active mainnav navigation entry is not highlighted when running tracd (was: Active navigation entry is not highlighted when running tracd)
     7}}}
    48
    5 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.
     9Note 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 both in the subject and in the body of the message.
    610
    711{{{