| Table of Contents |
|---|
Summary
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 for this feature is when you depend on the event's context (containing 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.
...
Recipients scripts can be added to 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 a CC recipient.
Velocity contexts and notification mechanisms remain the same in all three notification types (Issue, Ad-hoc and Post-function notifications).
...
| Note |
|---|
Adding a group by script ( |
| Info |
|---|
In order to know the account id of a particular user, you can use the User Finder tool in JEMH Cloud → Tools → Cloud > Tools > User Finder. Copy and paste the account id into the script when adding users programmatically. |
...
You can see these events and the processing outcome by going to JEMHC configuration → > Auditing → > Events.
...
After being processed, an event will have a report showing the recipients resolved, notifications sent and the any problems or warnings found. Use these reports to validate the recipients the script has resolved. The below is an example of an Event Report taken from JEMHC → > Auditing → > Events. As you can see, one of the notification recipients has "(Script)" after their address, which signifies that this recipient was added due to the use of a velocity script.
...