Normally, RMTrack does a brute force HTML to Plain text conversion to ensure each e-mail includes both plain text and html. However, the HTML to plain text conversion does not always produce nicely formatted results.
For those cases where clients wish to explicitly define a plain text e-mail body, this checkbox will open a secondary plain text editor (see below) where an explicit plain text e-mail body can be defined.
Subject Line
Each e-mail must have a subject line. Issue fields can be embedded in the subject line by enclosing the field name in square brackets e.g. [fieldname]. The field values will be resolved when the e-mail is sent. For example:
"Issue number [IssueId] has been created and assigned to [AssignedToUser]"
A list of available fields is provided on the right side of the page.
HTML Message Body Editor
The the body of the e-mail can be entered using the HTML editor supplied or you can enter (or modify) the source HTML by clicking the Source button in the editor menu bar. HTML formatting is available buy clicking the appropriate button in the editor menu bar, for example: tables, bold, italic, underline, alignment, lists etc.
Issue fields can be embedded in the subject line by enclosing the field name in square brackets e.g. [fieldname]. The field values will be resolved when the e-mail is sent. For example:
"Issue number [IssueId] has been created and assigned to [AssignedToUser]"
A list of available fields is provided on the right side of the page.
NOTE: Comment log type issue fields will only use the last comment added to the issue.
WARNING: Care must be taken when designing e-mail templates. Certain users may not have view access to certain fields (see Field Level Security). E-Mail notifications do not take field level security into account and will send the field information to any designated recipient.
Available Fields
....
A list of all Issue Fields will be displayed. Issue field data can be inserted into the body of the e-mail or into the subject line, by enclosing the field name in square brackets e.g. [fieldname]. The field values will be resolved when the e-mail is sent. For example:
"Issue number [IssueId] has been created and assigned to [AssignedToUser]"
Note that the list can be collapsed by clicking the arrow at the top left.
Available Macros
Several macros are available to be included in the e-mail. Like the issue fields, they must be enclosed in square brackets and will resolve when the e-mail is sent. The available macros are:
[IssueURL] - This will resolve to a link back to the issue that triggered the e-mail notification and is useful to provide easy access to the issue. The macro can be used as is, or as part of an HTML href tag which can be added by using the "chain link" button on the editor menu bar. For example, in your e-mail body you might put:
"Issue number [IssueId] has been ... " then select the text Issue Number [IssueId] and click the chain link on the editor menu. In the URL box in the pop-up put [IssueUrl] and set the Protocol to <other>.
[WebSiteURL] - This is a link to your RMTrack website e.g. http://www.yourcompany/RMT
[PasswordResetURL] - This is a link to the password reset page if your site uses e-mail password resets
Both the of the "Name" macros have variations that include plurals and upper/lowercase. For example: [Name:issues] will make the name for issues all lowercase and plural i.e. tasks but [Name:Issue] will make the name begin with uppercase and no plural i.e. Task
Test E-Mail
The Test button allows you to send a test e-mail so that you can view the actual result of the template. When doing a test you will be asked for an e-mail address an issue # for the test.
in the editor menu bar. HTML formatting is available buy clicking the appropriate button in the editor menu bar, for example: tables, bold, italic, underline, alignment, lists etc.
