Example Scenario
...
Option 1: JEMH Profile Driven
This method is a simple check-box made with setting: Profile > Configuration > Notification > Notify Users on Issue creation. This is driven by JEMH rather than JIRA, and will cause the originator of the email to receive an update. The content of this update is by default the ISSUE_CREATED template. Alternative content can be generated by creating a custom Issue Event Template Set for ISSUE_CREATED,
...
see /wiki/spaces/JEMH/pages/2850840. Make sure to give
...
the template a
...
unique name so
...
it can be easily identified. The Profile then needs to be updated, setting Configuration > Email > Issue Created TemplateSet, which will present all available ISSUE_CREATED TemplateSets, the DEFAULT means the system template.
Advantages | Disadvantages |
---|---|
|
|
|
|
Option 2: Use JEMH Event Listener
...
The implementation of a simple acknowledgement using a Custom Event is documented in Send a simple acknowledgement.
Advantages | Disadvantages |
---|---|
|
|
To make the notifications reflect full ISSUE_CREATED notification content, the TemplateSet referred can generated as follows:
- Create a new ISSUE_CREATED Issue Event Template Set
- Edit, and:
- set the title to 'Custom Issue Created Template'
- change the eventType to be the custom event (created in JIRA as part of the tutorial above)
- Save
- If using JEMH for JIRA user notification
- Check that ISSUE_CREATED event is not enabled for either non-JIRA or JIRA users
- Check that the JIRA Project notification scheme is not enabled and that it is selected
- In the IssueListener Project Mapping, for non-JIRA and JIRA users notification, select this Template set for the Custom Events template.
...