I second this. To me, the primary purpose of emails in a bug tracker is to convey updates. If when reading an update email one has to repeatedly skip large blocks of information that has not changed, it lowers the usability of the email feature drastically.

That said, I'm sure there are folks who prefer the entire contents of a bug to be sent in an email. That, in addition to the volume of other individual feature requests pertaining to the email feature, leads me to believe that perhaps a major redesign of the email feature is in order, to accommodate very detailed customization -- perhaps through a set of template-style config files?

Resolved with patch included in issue 0004278

well, the summary email is interesting, but I like much more the way Bugzilla works: you get only the information you need, and not the whole history of the bug..

+1 vote for diff email (if it counts....?)

@ DGtlRift:

This looks anything but fixed, so I'm moving Resoution to "open"

Are you still working/willing to work on this?

Unassigning this after more than 4 years being assigned without a resolution.

Okay, I've been on quite a haitous for some time burried in a corporate project - but I will have some time in the next couple of weeks to put some effort into this. @Giallu, I've seen the wiki notes, but there doesn't seem to be a consensus on what should be done? Is this dependent on a templates system or is it still stand alone?

sorry for the delay. here is my 0.02 on the topic.

I would not consider a templates system to be a prerequisite for implementing this. We just need to not hardwire presentation code ion the feature's logic so we can later plug-in whatever templating system we may add to mantis.

Please feel free to have a look at the current code and see if you can make up a plan, I will be more than happy to help you on this.

Unassigned after years of inactivity