Jira user creates an issue via email with additional participant and attachment
Scenario
This scenario will cover Jira user/portal user issue creation with attachment and additional participant. Also, the issue will be assigned to the default Assignee. We will see the difference against using Recipient Type: To and Bcc options. How 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:
Additional settings which are not present in above screenshot:
Recipient Type: - To
Notify Users Of Their Actions When Update: - enabled
Issue Creation
Issue | Issue History |
|---|---|
|
|
Events
As we can see from Jira issue under History tab, after issue has been created, the following events happened (changed Assignee, updated Labels). Therefore, the above screenshot indicates that webhook events have been merged [3] to reduce email volume.
Recipient Type: TO
Event Report
If the Recipient Type is set to TO under notification mappings, then Event Report indicates that 3 email has been sent to the Current User, Request Participant and Assignee. Also, under Auditing > Outbound Messages view we can see that 3 emails has been sent
Recipient Type: Bcc
Event Report
The same events but this time Recipient Type is set to Bcc, we can see in the above screenshot that 1 email has been sent summing up 3 recipients, which will reduce the message usage. Also, under Auditing > Outbound Messages view we can see that 1 email has been sent
The Report will indicate who was notified
Related articles
https://thepluginpeople.atlassian.net/wiki/spaces/JEMHC/pages/2552889351