...
To configure which one to use, open the Settings page of the Email This Issue configuration screen, scroll down to the field Email Editor.
JETI supports creating rich text emails via JEditor, a popular Rich Text Editor add-on for JIRA.
JIRA Editor
This is the default wiki markup editor used in JIRA by default for text fields.
Email This Issue Rich Text Editor
JETI's embedded rich text editor provides WYSIWYG editing.
Just explore the menus and toolbars to see how to
- link issue attachments, add images and links, etc
- edit in full screen
- quick preview your content
The use of this editor type does not require additional addons or licenses.
Things to Know When Using the embedded Rich Text Editor
- You don't have to change you templates to render Rich Text emails
- Email log displays rich text emails correctly
- If users enable JETI to add comments to issues when sending emails, please be aware that the rich text email body will be escaped and fairly unreadable unless you enable JEditor renderer for comments in JIRA Field Configuration.
This is because JIRA always escapes HTML in comment text. - If email format is forced to set to Text, rich text content will be escaped in the email making it hard to read
JEditor
This is a well known editor available in the Marketplace for many years now.
| Note | ||
|---|---|---|
| ||
In order to create rich emails, you must install JEditor and obtain a license key for it. |
Once JEditor is installed, you must enable it in JETI Configuration.
Open JETI Configuration Tab:
Then Enable JEditor:
When yo compose the email, JEditor is loaded and Email Body is replaced with the rich text editor:
Email listed in Email Audit Log:
Things to Know When Using JEditor
- You don't have to change you templates to render Rich Text emails
- Email log displays rich text emails correctly
- If users enable JETI to add comments to issues, please be aware that the rich text email body will be escaped and fairly unreadable unless you enable JEditor renderer for comments in JIRA Field Configuration.
This is because JIRA always escapes HTML in comment text. - If email format is forced to set to Text, rich text content will be escaped in the email making it hard to read
...