In JEMH Cloud, Jira users by account ids, Jira groups and Email Jira users, groups and non-Jira user email addresses can be dynamically added as recipients of Issue, Ad Hoc or Post Function notifications using Velocity scripts. The main use case of for this feature is when you depend on the event's context (like the issue data) to conditionally add extra notification recipients. This allows you to do things such as notify managers when the issue's priority is Critical.
It's recommended to use the standard recipients configuration (notify reporter, notify watchers, etc.) when the recipients are not conditional.
Conditional
...
recipients
...
Issue
...
event notifications
To add conditional recipients in notifications, go to Notifications → Issue and edit your mapping by clicking on the Cog icon.
...
| Info |
|---|
JEMHCloud doesn't duplicate emails. if an email has been resolved by several configurations (static or script), the recipient will receive the notification only once. |
...
Ad-
...
hoc and workflow post-function notifications
Recipients scripts can be added to AdHoc Ad-hoc and Post Function Notifications as TO, CC or BCC. Each script resolves the recipients for each type. For example, a recipient added via the CC script will receive the email as CC.
Velocity contexts and notification mechanisms are remain the same in all three features notification types (Issue, AdHoc Ad-hoc and Post Function -function notifications).
Examples
The following examples can be used in Issue, Adhoc Ad-hoc and Post Function notification-function notifications:
| Code Block | ||
|---|---|---|
| ||
##If the event is an issue created event, notify a non-Jira email address
#if ($context.webhookEvent.textValue() == "jira:issue_created")
$recipientUtils.addEmailRecipients("scripted@example.com")
#end
##If issue priority is blocker and type is bug, notify Jira user johnfixall
#if ($context.issue.fields.priority.name.textValue() == "Blocker" && $context.issue.fields.issuetype.name.textValue() == "Bug")
$recipientUtils.addUserRecipients("557058:a8d85d49-2566-47f4-9f31-861930631857")
#end
##If issue is of project SD, notify email users devLead@mycompany.com and testLeader@mycompany.com
#if ($context.issue.fields.project.key.textValue() == "SD")
$recipientUtils.addEmailRecipients("devLeader@mycompany.com,testLeader@mycompany.com")
#end
##If issue priority is Major, notify support level 3 group
#if ($context.issue.fields.priority.name.textValue() == "Major")
$recipientUtils.addGroupRecipients("support-level-three")
#end
##If issue priority is Minor, notify support level 1 and level 2 groups
#if ($context.issue.fields.priority.name.textValue() == "Minor")
$recipientUtils.addGroupRecipients("support-level-one,support-level-two")
#end
##If operation was made by CEO user or issue reporter's CEO user, notify management
#if ($context.user.key.textValue() == "ceo" || $context.issue.fields.reporter.key.textValue() == "ceo" )
$recipientUtils.addGroupRecipients("management")
#end |
| Note |
|---|
Adding a group by script ( |
...
Testing
Issue notifications can be tested by creating or updating Issues issues through the Jira user interface. Alternatively, you can use JEMH Cloud's email processing or JEMH Cloud's test cases features. These actions will generate issue events that JEMH Cloud listens for.
...
| Warning |
|---|
Re-running an event will resend the emails. To avoid spamming your users, use a test mail server like mailtrap or disable the mail server by going to Notifications → Message Outbound. |
Related
...
articles
| Filter by label (Content by label) | ||||||||
|---|---|---|---|---|---|---|---|---|
|