...

From version 1.7.2, JEMH has the ability to allow scripted decision logic at the Template level on whether or not a given notification should be sent by using the $jemhUtils.setInhibitSending(boolean) method.  The script itself can be as simple or complex as you need.

/wiki/spaces/JEMH/pages/2850840 are the raw Velocity mark-up content for email notifications.  For more information on what Velocity is and how it is used, see the official user guide here.

Project Mapping Solution

If you do not want to customize templates, it is possible to add inhibition logic at the ProjectMapping config level, see:

• Change the EventID or Ignore an Event

The Velocity Context

The usual velocity context references are available to help you script your decision logic, there is also a helper class available $jemhUtils , see the API link below for additional methods available:

...

#if ($!recipientEmail && $recipientEmail.matches(".*@blah.com"))
  $jemhUtils.setInhibitSending(true)
  #set ($inhibitedMsg = "Recipient is inhibited: "+$recipientEmail )
  $jemhUtils.setInhibitSendingReason($inhibitedMsg)
#else
 .. the rest of the template, no point rendering
#end

Inhibiting by user group

#if($groupManager.isUserInGroup($recipientUser, "jira-administrators"))
  INHIBITED
  $jemhUtils.setInhibitSending(true)
  $jemhUtils.setInhibitSendingReason("Inhibiting notifiction to jira-administrators")
#end

#if($groupManager.isUserInGroup($recipientUser.getDirectoryUser(), "jira-administrators"))
  INHIBITED
  $jemhUtils.setInhibitSending(true)
  $jemhUtils.setInhibitSendingReason("Inhibiting notifiction to jira-administrators")
#end

Inhibiting by user picker custom field

##Customfield id format example customfield_00000
#set($inhibitTheseUsers = $issue.getCustomFieldValue("<your_custom_field_id>))

#if($inhibitTheseUsers.contains($recipientEmail.getUser()))
  $jemhUtils.setInhibitSending(true)
  $jemhUtils.setInhibitSendingReason("Inhibiting notifiction to <your_custom_field_id>")
#end

Inhibiting the ISSUE_CREATED notification when the issue was created by email

...

Once you've created the custom field, make a note of the ID on the Cog > Configure link, (hover, look at URL), it will be something like:

The Custom Field default value for interactive users:

...

Once this has been done, the following velocity script can be inserted into a custom Template Set.  This script will inhibit the sending of the notification when the issue is submitted via email but allow the notification through if it was created interactively.

#if ($!issue.getCustomField("customfield_10100") && $!issue.getCustomFieldValue("customfield_10100")) 
    #if ($issue.getCustomFieldValue("customfield_10100")=="Email")
        $jemhUtils.setInhibitSending(true)
        $jemhUtils.setInhibitSendingReason("This notification was inhibited because the issue was created by email")
        <h3>Create by Email</h3>
    #else
        <h3>Created Interactively</h3> 
		... Your email template here
	#end
#end

#if ($!customFieldManager.getCustomFieldObject("customfield_10100") && $!issue.getCustomFieldValue("customfield_10100")) 
    #if ($issue.getCustomFieldValue("customfield_10100")=="Email")
        $jemhUtils.setInhibitSending(true)
        $jemhUtils.setInhibitSendingReason("This notification was inhibited because the issue was created by email")
        <h3>Create by Email</h3>
    #else
        <h3>Created Interactively</h3> 
		... Your email template here
	#end
#end

...