| Table of Contents |
|---|
Notification Mappings
JEMHC offers the ability to send issue event notifications across the following transport:
Email Notification Mapping
Notifications
Notifications are driven by WebHook events sent by JIRACloud, they are much more limited in terms of 'what' the events are than JIRAServer provides, for issues there are only:
...
The Generic theme is a reduced version of the JIRA theme, more suitable for simple email based support (primary use case).
Create
...
an Email Notification Mapping
Navigate to the Notifications > Issue screen, select Create to get a dialog: tab in JEMHC, on the left hand side will be a list of available notification mapping types. Select the Email Notification Mapping and then select Create button.
The Dialog:
NOTES:
- In this example, HTML notifications were selected, this also allowed Wiki Rendering to be enabled - this allows wiki markup in JIRACloud to be rendered in outbound notifications.
- The Generic theme was selected
- Issue Deleted template was deselected, removing notifications of this event
- Projects were changed from 'all' to just the Support project
...
Further down the dialog:
NOTES:
...
A summary of this is listed:
Changing the Sender Email Address between issue types
You might want to have a different sender email address for each type of issue type e.g. bugs would come from bugs-project-one@email.com, and tasks would come from tasks-project-one@email.com. In the following example we're going to utilise the value set by a Custom Field Defaults configuration to change the sender address used in an outbound notification. This presumes that you're familiar with how to configure a Custom Field Configuration (if not, this page will teach you how - Custom Field Defaults).
Preamble
- A custom field exists for all the issues within your project. It will contain the sender email address.
- A Custom Field Default exists for your project. This results in all issues that are created from inbound emails by JEMHC having a value for the custom field.
- The Custom Field Default is different for each issue type, e.g. tasks are tasks-project-one@email.com and bugs-project-one@email.com.
- This can be configured by having multiple rules within your non-default project mapping. See Rule Driven Project Mappings.
Once the items in the preamble are out of the way it's really easy to vary the sender email address between issue types. All you have to do is go into your email notification mapping and find the field called 'Sender Email Address Custom Field' under the 'Sender' section. Here's a picture of it configured to look inside a custom field called 'Custom Field'.
When this field is populated the email notification mapping will use its value as the sender address when sending out email notifications. If the custom field is left blank on the Jira ticket then the sender address within the Message Outbound configuration will be used instead. You can find this by going to Messaging → Outbound → Message Outbounds. Here's a picture of my message outbound.