...
By default configurations in JEMH when the email has been sent and the issue is created in Jira, received issue creation notification will create a new email Thread and all further communication will be associated with this newly created email Thread. In order to associate the issue creation notification and all other event notifications with the initial email sent requires to apply additional configurations. The following example is based on using a Gmail email client.
Gmail requirements to satisfy the email threading
In order to for email to be threaded in Gmail conversation view, the following must present in the notifications:
...
You will need to create a custom Issue Create Event. Please see the following documentation on how to add/create a custom event: Adding a custom event
...
To add recipients to the event, you can do it on the same page under Actions > Edit notifications
...
Then scroll down to yours your custom event and click on Add. In this example, the following recipients has have been added
...
Once you have added all desired recipients, make sure that Project Notification Scheme has been disabled. JEMH requires that the projects for which JEMH should handle notifications have no notification scheme selected, as leaving it enabled will generate JIRA standard notifications as well as JEMH notifications. This can be done through JIRA > Project Administration > Notifications > Actions > Use a different scheme > Select Scheme (none):
...
In the next step we set ‘something’ on the issue to indicate that JEMH created the issue, then during notification we can ‘ignore’ the JEMH ISSUE_CREATED notifications as we also expect the custom event.
4.
...
Creating a custom field
After enabling a custom event and enabling JEMH notifications, JEMH will actually sent two notifications. The first in response to Issue Created, and the second due to Custom Event. You would normally want to inhibit the notification when it was driven by JEMH, rather than an interactive user. The suggested approach is to set a Custom Field default value on Create to identify the source as JEMH, this Custom Field value can then be detected int the JEMH notification section and used to filer/stop the Issue Created notification.
...
In order to retain the same email subject as the initial email, you will need to create a custom templates for each issue event you will need to send a notifications and remove the IssueKey from the subject.
...
| Info |
|---|
Only for the Issue Creation event, you will need to select your created custom event and for all other a default ones |
...
By default the Subject contains IssueKey
...
IssueKey needs to be removed in order to retain the same email subject as the initial one
...
6. Setup Outbound Notifications
...
Event Template Selection
Select all your custom templates for the corresponding events to be fired.png?version=1&modificationDate=1624967835419&cacheVersion=1&api=v2&width=272)
Result
Initial The initial email has been sent to create an issue in the Jira
.png?version=1&modificationDate=1624968135534&cacheVersion=1&api=v2&width=161)
.png?version=1&modificationDate=1624968135534&cacheVersion=1&api=v2&width=156)
...
Issue The issue has been created and the custom field has been populated withe with the Email value
.png?version=1&modificationDate=1624968266736&cacheVersion=1&api=v2)
...
Issue creation notification has been added to the initial email thread
.png?version=1&modificationDate=1624968383515&cacheVersion=1&api=v2)
...