Is it possible to customize the email body?

[ATX]

I would like the email notifications to be a bit more specific. Is it possible to have the verbiage in the body of the email to coincide with the action taken?

[atrol]

Please give an example for what you want.
I think the email body reflects pretty good what is happening with an issue

[ATX]

The body of the e-mail for example says the issue has been assigned, but does not say to who. In the case when a note is added, the e-mail alerts us a note has been added, I would like it to grab the note and throw it in the body. When an update was made, it would be helpful to notify users what was updated and so on. This specificity in the e-mail body provides information to users preventing them from having to log into the application to view the change.

[atrol]

Which version of MantisBT do you use?
I am using 1.1 and 1.2 and I get most of the information you can see when viewing an issues also when an email is sent.

[ATX]

I believe we are using 1.1.7. Here's the email I get when a note is added:

A NOTE has been added to this issue.
======================================================================
http://iedddddddd/mantisbt-1.1.7/view.php?id=283
======================================================================
Reported By:
Assigned To:
======================================================================
Project: Issue Tracker
Issue ID: 283
Category: Database Architecture
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
Target Version:
Due:
======================================================================
Date Submitted: 03-10 10:46
Last Modified: 03-10 14:12
======================================================================
Summary: 0283: File size for attachments in Mantis does not
accomodate OPTs documents
Description:
Increase the file size in for attachments in Mantis



As you can see, without going into the issue I don't know what the note is or who it might be directed at.


Here is an example of an email from an update:

The following issue has been UPDATED.
======================================================================
http://iedddddddd/mantisbt-1.1.7/view.php?id=283
======================================================================
Reported By:
Assigned To:
======================================================================
Project: Issue Tracker
Issue ID: 283
Category: Database Architecture
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
Target Version:
Due:
======================================================================
Date Submitted: 03-10 10:46
Last Modified: 03-10 14:18
======================================================================
Summary: 0283: File size for attachments in Mantis does not
accomodate OPTs documents
Description:
Increase the file size for attachments in Mantis


Again, as you can see there is no way to know what was updated without going into the request. The email also comes through for "This issue has been ASSIGNED" but doesn't say to whom, so again users have to log in to take a look


Does the version impact the ability to customize the notification?

[atrol]

I believe ...

Wrong forum?

To be more serious:
Do you have any own configuration, third party plugins, .... ?

Is the user which receives the mail able to view the information "Reported By:" and "Assigned To:" when he is logged in to MantisBT and viewing the issue?

[ATX]

Yes, they are able to view when logging in. We have changed the e-mails to an HTML format and they now supply nearly the entire issue, a little overkill but closer. We are not using any plug-ins.....

[qatester]

I would like to know hot to customize the email subject and body too? I'd like to remove some of the fields (i.e. reproducibility, target version, etc.) that I don't use in the bug report.

[atrol]

AFAIK there is no other chance to customize the subject than to tweak the code of function email_build_subject in file core/email_api.php
There is already a feature request for this at http://www.mantisbt.org/bugs/view.php?id=8986