...
Ensure the following is conifgured in your User Section which can be found via JEMH Configuration> Profile > a Profile Item > Conifgure > User Section and follow the steps below with the screenshot below as a reference:
Set a Default Reporter user who will be used as the surrogate reporter for issues.
Ensure that the Create users option is disabled otherwise JEMH will create user accounts for the users (which we do not want in this scenario).
...
Create custom fields to hold data
JEMH uses two text type fields to store the Personal part of an email and the actual email address.As an example we will create the custom fields Sender Name and Sender Email Address. Create these now if they don't already exist. In Jira navigate to Jira Administration > Issues > Custom fields. Then, click the Add custom field button:
 |
Select Text Field (single line) and hit Next
 |
Set the name of the field to be Sender Name and select Next.
 |
Configure which issue types and which projects the custom field should apply to.
 |
Update the screens on which the field should appear and select Update
 |
Repeat the above steps to create the "Sender Email Address" field. You should now have 2 custom fields created. One for the sender address, and one for their "personal" name:
 |
Configure profile to add non-Jira sender to custom fields
Go back to your Profile via JEMH Configuration > Profiles > a Profile item > Configure > Email and select the Email Section and choose the appropriate Operating mode:
 |
Locate the Sender processing: non jira-user section via the Sender Processing Tab in the previously mentioned Email Section and select the newly created custom fields:
 |
Hit Save and check the values are reflected:
...
From the JEMH Configuration screen, select the Event Listener/Notifications tab via JEMH Configuration > Notifications:
 |
Next, add a Project Mapping for your target project. Navigate to the Non-Jira notifications tab via Transports Section > Email Tab > Non Jira notifications and then New Project Mapping to create a Project mapping.
 |
| Info |
|---|
There is complete isolation between JEMH Profiles and the Event Listener/Notifications. The Event Listener has no way to know how an issue arrived, hence Project/Template selection is required outside the normal Profiles. In order for events to be processed by the JEMH Event Listener:
In the project mapping you can configure notifications for both JIRA and non-Jira users, both configurations are independent from each other (e.g. non-Jira users can be notified of certain issue event while Jira users wont be). |
...
Project Keys: Enter the KEY of your target project (e.g. TEST).
Notification Format: Set the format of the notification (e.g. HTML).
CSV email Custom Fields: Enter the name of the custom field used used to store non-Jira user address - "Sender Email Address".
 |
Save your configuration changes
...
Edit the Project Mapping once more, and go to the Event Template Selection section. Select notification templates for the issue events you want the non-Jira users to be notified of.
 |
Press the submit button when you are done.
...
If it is not already enabled, now is the time to enable the Event Listener via the previous Notifications screen > Issue Events Section > Edit Icon (Pen):
 |
 |
And verify:
 |
Profile driven notifications
...
Only a simple change is needed for the issue creation notification to be triggered and sent by the JEMH profile. Under the Notification section in the JEMH profile, change the Notify Users on Issue setting to Non-Jira sender.
Defaults | Configure Non-jira user notification | After Update |
|---|---|---|
 |  |  |
Create issue notification content
| Info |
|---|
By default JEMH will use the default Jira issue created template and the email will be set in the TEXT format. The profile can be set to send HTML emails and use custom templates under |
 |
Verify that non-Jira users can receive notifications
...
An initial issue created event should be sent out, it may take a minute to flush out of the queue. Here is an Issue Created Custom notification:
 |
Now go and comment on the issue as a Jira user. The issue event should fire, be rendered and also sent to the queue, which also will be dispatched a little later.
Here is a standard Issue Commented notification:
 |
Related articles
| Filter by label | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|