...
A valid license is present (once a subscription is active, cancelling it and starting a new trial will not work). To determine the app’s current license status, go to Jira settings > Apps > Manage apps and expand the JEMHC entry.
A Notification Mapping for the related project (or for all projects) is configured in the app. This can be determined by navigating to JEMHC > Notifications. For example, here is an email mapping:
...
Jira bulk changes
When a bulk change happens, your Jira instance will send a webhook for each and every issue update. This can create a flood of notifications if you check “Send mail for this update”. After many years of lobbying, Atlassian finally included this flag in the webhooks we receive.
By default, “Send mail for this update” is unchecked, meaning JEMHC will drop the webhook as soon as it is received, no mail will be sent. If “Send mail for this update” is checked, a notification webhook will be sent for every transition made against every selected issue.
Why Jira still sends all your issue data to us when no JEMHC license is present
...
Info |
---|
Additional settings which are not present in above screenshot:
|
Issue Creation
Issue | Issue History |
---|---|
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 [1] in the 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.
...
Page Properties | ||
---|---|---|
| ||
|