| Table of Contents | ||
|---|---|---|
|
...
| Expand | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||
|
...
In order to support email integration for users with no Jira user account, JEMHC needs to store email addresses in custom fields. Select what custom field is used to store a non-Jira email sender's name and address. You can also choose what where additional user email recipients (CC and BCC) are stored.
...
.
Owing to choices Atlassian made long ago, the default readonly “Email Participants” field created by the app (should be a TEXT type) was implemented by Atlassian as a single line field, this may impact you if more than a handful of email-only ‘additional recipients’ would be involved. If you plan to use this feature extensively, you should pre-create another “Email Participant Addresses” field or similar that is of type text multi-line, then, in the wizard, pick that instead of the bundled field that is limited to 255 chars.
...
If you see a warning that a field isn’t present on the projects issue screen (as above), click the link in the message. You will then be able to associate the field with the appropriate screen related to your project
...
Until the mail server setting has been used, its status will be 'unknown'. To validate this, use the ▸ ping action, loacated under the … more actions icon. Here, the outcome is that the SMTP server is now Online (this would have happened anyway on first actual usage):
...
Recent outbound notifications can be reviewed through: Auditing > Outbound Messages, you can see the outbound message configuration tests sent using ▸ ping.
...
The Auditing > Events view shows the webhook events sent by Jira, and indicates whether they were handled or not. Any Jira issue actions that trigger events matching the selected notification mapping(s) will be shown in the Events view:
...