Content Comparison

Scenario

You want to prefix incoming email content processed by JEMH, either issue description during create or a comment.

...

Any TemplateSet can be edited and customized, the default and advanced are shown below:

Default	Detailed

Image Removed

Image Added

Image Removed

Image Added

The comment header template can be previewed by entering a valid issue key into the Preview Context Issue Key box and then pressing the icon under the comment header text field.

Once a Comment Header TemplateSets has been created, they are referenced through individual Configuration Profile > Email > Templates:

...

To select a comment header, edit the Email section within the relevant Profile by clicking on the pen icon

...

To illustrate this we'll use a quick JEMH Test Case, the default will work:

Create Test Case	Created Test Case	Test Case Execution Result
Image Modified

Image Removed

Image Added

Image Removed

Image Added

Here is the detailed header used in the example, prefixing the description of the issue:

...

#if ($!issue)
	WE ARE IN ISSUE COMMENTING MODE
#else
	WE ARE IN ISSUE CREATING MODE
#end

Getting the Application User associated with the sender

#set ($fromUser = $jemhUtils.getUserByEmail($fromAddress.getAddress()))
#if ($!fromUser) Sender User [name=$fromUser.getName(), key=$fromUser.getKey(), directoryId=$fromUser.getDirectoryId(), displayName=$fromUser.getDisplayName()]#else No User Found for $fromAddr #end

Context

The Context is available for review at edit time, you can use it to link off to Javadoc for Jira API objects as needed - our jemhUtils class is also available, exposing things like the mailbox catchEmailAddress.

Related articles

...