| Table of Contents |
|---|
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 |
|---|---|
  |   |
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
...
Create Test Case | Created Test Case | Test Case Execution Result |
|---|---|---|
 |   |   |
Here is the detailed header used in the example, prefixing the description of the issue:
...
| Code Block |
|---|
#if ($!issue) WE ARE IN ISSUE COMMENTING MODE #else WE ARE IN ISSUE CREATING MODE #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.
context variable | Data Type | Description |
|---|---|---|
message | the raw message object | |
subject | java.lang.String | the Subject text |
jemhUtils | JEMH Helper class | |
| java.lang.String | The Mailbox catchEmailAddress |
toAddresses | the to: addressees | |
ccAddresses | the cc: addressees | |
bccAddresses | the bcc: addressees (don't expect many here!) | |
allAddresses | all addressees | |
body | java.lang.String | the post processed (html > markup) content – :warning: since JEMH 2.7.36 for Jira 7.10.x |
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...