| Table of Contents |
|---|
Scenario
In this scenario, the Jira user/portal user creates an issue via email with an attachment. For this scenario Recipient type setting is set to TO under Notification MappingsHow to analyze the outcome of the events please review under How Jira events turn into emails.
Notification Mapping configuration
The following notification mapping configuration has been used:
...
| Info |
|---|
Additional settings which are not present in above screenshot:
|
Issue | Issue History |
|---|---|
 |   |
Events
...
Jira sends a Webhook sent to JEMHC, where it will be stored if the license is valid and there is a Project Mapping for the related project (or all). The [2] int he screenshot below indicates the number of webhook events we received/merged which is how JEMHC will ‘batch’ multiple events in a minute window together to reduce email volume, and maximize Plan allocation usage.
...
Events stored by JEMHC are shown in Auditing > Events, each event has some context options available, Run will cause the event(s) to be consumed immediately, the event can be deleted, we can save a copy of the event as a Preview Context (for template preview or exported for support purposes:
...
Event Processing
After a minute, events received in the last minute for each issue are processed, the event is updated to indicate what notifications were sent (email), see the Report from the context menu for more info:
...
The Auditing > Outbound Messages view shows a filtered view of all notifications ( the default is SMTP, so other variants such as Office365 EWS (Exchange Web Services) are not shown by default, select Type: All to see all kinds of notifications, here, we can see the recent email
...
Each items has a context menu accessed through the cog on the right. From the email item:
...
When the issue has been created, we can see under the Issue view for the History tab, 3 events happened. Therefore, the above screenshot indicates that webhook events have been merged [3] to reduce email volume.
Event Report
...
The Event Report indicates that 1 email has been sent to the Reporter. Also, under Auditing > Outbound Messages view we can see that one email has been sent
...
The Report will indicate who was notified, here the '@thepluginpeople.com is the outbound sender mailbox address.
...
A restricted view of the mail is also available, so you can see ‘what’ content was sent, 'what' notification event has been sent (and see it differ between different recipient notifications):
...
Reviewing the actual sent mail
...
Querying mail sent through the Analysis feature
Available through Auditing > Analysis, we provide the ability to query mail received/sent in various ways. For example here, we can set the “Issue Key” to be JEMHCTEST-13, and set the Group By to be “Type”, which shows the Message Size and the data used (deducted from the Plan capacity). Instant Message notifications are free (do not count toward Message volume or Data usage).
...
If you went back the the Outbound Message Auditing view, you could export the mail, and check its file size:
...
You can see that the size of the physical email is larger, this is because of additional email headers that were involved, but we don't consider this for data usage, hence the smaller number should via Analysis relating to the content + attachment data size prior to encoding. There is always a slight difference in outbound notification ‘size’ actually and what JEMHC deducts, its done prior to encoding for simplicity.
Monitoring Usage
The Licensing > Usage shows a live usage summary of message volume and data.
JEMHC can also notify you of relative usage (via Usage notification warning threshold % ), whereby if this value was 50%, and you were notified of this earlier than the middle of the month, on balance, capacity looks to be enough, if you get this on day 1, its probably not going to last much longer. Recipients are listed through Licensing > System Notifications > (Email Addresses | Users).
...
Related articles
How Jira events turn into emails
...