Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Email This Issue supports multiple email editor types when composing manual (adhoc) emails in the email screen:

  • JIRA wiki markup editor
  • TinyMCE based rich text editor (comes with Email This Issue out of the box)
  • JEditor (rich text editor addon)

To configure which one to use, open the Settings page of the Email This Issue configuration screen, scroll down to the field Email Editor.

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. 

JEditor licence key not included

In order to create rich emails, you must install JEditor and obtain a license key for it.


When yo compose the email, JEditor is loaded and Email Body is replaced with the rich text editor:

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

 

  • No labels