Combined interactive and remote email issue creation
Scenario
If the project in which you are creating issues and for which the JEMH Event Listener is configured to handle JIRA user notifications is to be used by both JIRA interactive users and external email users, then, interactive users creating issues will not get ISSUE_CREATED events because they aren't enabled (when following the From Scratch guide).
Solution
Use a hybrid configuration splitting the issue creation notification out and driving it via Profile:
1. Set JEMH Profile Notifications > Notify Users on Issue creation : non-jira (or all) (in this case, Non-JIRA means without 'right to use')
2. Do not set JEMH Profile Notifications > fire the custom issue event
3. Enable the ISSUE_CREATED event in the JEMH Event Listener project mapping, disable the custom event.
Issue Creation Outcome
For issues created by remote non-jira users (with accounts but without right to use) they will be notified of issue creation via the Profile Notifications > Notify Users on Issue creation
JIRA assignees set by JEMH will be notified of issue creation. They will also receive an ISSUE_UPDATE event with the related custom field/other changes like attachments.
For interactive JIRA users, they will be notified via the Event Listener ISSUE_CREATED event.
If during issue creation, the interactive user added any watchers or users to multi-user pickers that are referred from the Project Notification Scheme, they should be notified via the Event Listener method too.
Reporters are a special case. If the JIRA Project associates a notification scheme, reporters will be filtered due to user preference about 'notify me of me actions'. To make this work the JEMH Event Listener has to be used instead of the Project association, setting the Notify Me Condition to forSelectedEvents and set the Notify Me Events, to be Issue Created:
Checklist of actions to setup redirection of notifications from 'JIRA' users in the Event Listener to 'Non JIRA users', enabling restricted notifications:
Assumption: non-JIRA account holders, must all be a member of a specific group, referred here as nonjira-users.
Disable the built-in Jira Notifications for the Project
For the JEMH Event Listener, set-up a Project Mapping for each project
Use our default notification scheme (with the JEMH 'post-create issue' clone template)
Group restriction: nonjira-users
Group restriction condition: Treat user with group as non-jira
Define the template sets which apply to Jira (Full set) vs Non-Jira