Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

Notification Mappings

JEMHC JEMH Cloud 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 onlyIssue events are sent to JEMH Cloud as webhooks by Jira. They are split into 3 types:

  • Created

  • Updated

  • Deleted

There are also a range of system notifications.

Themes

Notifications in JEMHCloud JEMH Cloud are all themed.  There are two internal Themes available, JIRA Jira and Generic.  

...

Jira Theme

The JIRA Jira theme mimics the look and feel of JIRA Jira notifications.

Generic Theme

The Generic theme is a reduced version of the JIRA Jira theme, more suitable for simple email based support (primary use case).

...

Navigate to the Notifications tab in JEMHCJEMH Cloud, on the left hand side will be a list of available notification mapping types. Select the Email Notification Mapping and then select Create button.Image Removed

...

The Dialogdialog:Image Removed

...

NOTES:

  • In this example, HTML notifications were selected, this also allowed Wiki Rendering to be enabled - this allows wiki markup in

    JIRACloud

    Jira Cloud 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:Image Removed

...

NOTES:

  • A target audience of Email and

    JIRA

    Jira users is set

  • Custom fields (Sender Email Address and Email User Participants) are set

  • Attachments (outbound) included but limited to 2MB each, not more than 4MB per message

  • Sender Personal set to always be PPL rather than be set by the display name of the user making the change

The Participant User field above is a diagnostic entry, it allows a given user to be BCC'd on EVERY message generated.  When initially setting up this helps to:

  • validate messages are sent in response to changes

  • look and feel is appropriate / working as expected

Once happy with the outcome, you'll be pleased to remove yourself from this entry!

...