...
These messages will be added together to calculate your monthly quota. The total number of messages and the total amount of data (e.g. megabytes) will be tracked.
Action | Message Increase | Data Increase | Message Total | Data Total |
|---|---|---|---|---|
Email pulled into JEMHC from Message Source, processed and injected into Jira. | +1 | +1Mb | 1 | 1Mb |
Email pulled into JEMHC from Message Source, ignored because no recipients match the profile's catch-email address, not forwarded because of the profile's configuration. | +1 | +1Mb | 2 | 2Mb |
JEMHC receives a webhook from Jira, but ignores it because the Notification Mapping finds no recipients | +0 | +0Mb | 2 | 2Mb |
JEMHC receives a webhook from Jira, and sends it because the Notification Mapping finds recipients. The recipients have the same view-level, so it includes them in one email. | +1 | +1Mb | 3 | 3Mb |
JEMHC pulls in an email but finds that it doesn't satisfy the Profile's catch-email configuration and forwards it because of the profile's configuration. | +2 | +2Mb | 5 | 5Mb |
...
Blacklisting images and attachments using JEMHC's Blacklisting feature will decrease the data consumption of your messages. Blacklisting won't decrease the data consumption for inbound messages because JEMHC has to pull in the entire message to work on it. Blacklisting will only affect the data consumption for outbound messages.
...
Attachments on tickets will be included in outbound notifications. You can omit ticket attachments from outbound notifications with a setting found in the Notification Mapping.
...
Example involving inbound and outbound processing
This example goes through the process of JEMHC polling a mailbox where it discovers one email containing a 100Kb attachment. The total size of the email is ~140Kb. JEMHC automatically creates a ticket containing the attachment. The status of the Jira ticket is manually changed and JEMHC automatically sends out an outbound email notification including the attachment because a Notification Mapping exists to do so (See Create an Email Notification Mapping for how to do so). We then amend the Notification Mapping so that it won't include attachments and we trigger another notification.
Here you can see an essentially clean usage metric.
...
Then we process an email containing a 100Kb attachment. The total size of the email is ~140Kb.
...
The ticket is set to done triggering an outbound notification because an email Notification Mapping is present in this JEMHC configuration (not shown). By default the attachment on the ticket is included as an attachment in the notification.
...
Here we go into the email Notification Mapping and disable the inclusion of attachments.
...
We then replay the same event that triggered the outbound notification using the the Auditing view, and we can see that far less data has been used compared to the previous outbound email notification.
...
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...