The difference between email editors
PreviousSending manual emailsNextEnabling template categories so templates can be chosen on the Email screen
Last updated
Last updated
Jeti Email This Issue for server supports the following email editor types when composing manual (ad-hoc) emails in the email screen:
JIRA editor
The TinyMCE based Email This Issue Rich Text editor (comes with Email This Issue)
JEditor (A Rich Text editor add-on)
To configure which one to use, go to the General Configuration menu item under Settings and scroll down to the Email Editor field under Other Settings, and choose the desired one from the dropdown list.
This is the default wiki markup editor used in Jira for text fields.
Jira Email This Issue's embedded Rich Text editor provides WYSIWYG editing. The use of this editor type does not require additional addons or licenses.
In the Email This Issue Rich Text editor, you can:
Add issue attachments, images, links, and so on.
Edit in full screen.
Have a quick preview your content.
Important:
You don't have to change you templates to render Rich Text emails.
Email log correctly displays rich text emails.
If adding comments to issues when sending emails is enabled, be aware that the Rich Text email body will be escaped and becomes unreadable unless under Administration -> Fields -> Field configurations the Default Text Renderer is enabled for the Comment issue field. This is because Jira always escapes HTML in comment text.
If the email format is forced to be set to Text, Rich Text content will be escaped in the email, making it unreadable.
A well-known editor available in the Marketplace for many years now.
Important: The JEditor licence key is not included. In order to create Rich Text emails with JEditor, you must install and upload the app and enter the obtained license key for it. To do that, you need to have the Jira administrator role, and go to Manage apps under Jira administration.
Important:
You don't have to change you templates to render Rich Text emails.
Email log correctly displays rich text emails.
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 under Administration -> Fields -> Field configurations the JEditor Renderer is enabled for the Comment issue field. This is because Jira always escapes HTML in comment text.
If the email format is forced to be set to Text, Rich Text content will be escaped in the email, making it unreadable.
