...
The webhook must contain the security token (which is provided within the URL that is created by JEMHCloud) and a query parameter. The Query parameter must contain the Issue key and the AccountId of the user that performed the action in order to send the notification to the correct users.
| Info |
|---|
You can use Issue data (Jira format) within the Jira Automation as this will contain the relevant information. |
The issue key can be provided by using one of the following formats:
...
Go to JEMHCloud > Messages > Message Outbounds. Confirm that you have created a mail server connection.
If not then you will need to create a Outbound Mail connection. See the following page for more info: Message Outbounds (Email)
Go to JEMHCloud > Messages > Incoming Webhooks
Enter a name and leave the Action to Send Notification and the Post method
Enter the Message you want to add to the email notification body.
Add the recipients. In this case the assignee.
Press Save. The created Incoming Webhook will appear on the list.
Click on "Show URL" and select and copy the full URL. Automation for Jira will call that URL when executing an Automation Webhook action.
...
Go to your project > Project Settings > Automation > Create Rule
Select the Scheduled trigger
Enter the Cron expression 0 0 7 ? * MON-FRI
Enter the JQL rule status = "In Progress"
Uncheck the last checkbox so all "In Progress" issues are reminded, not only the changed one
Add a "Send web request" action
Paste the JEMHCloud Incoming Webhook URL and enter the custom data template. The resolved issue key will be posted in the HTTP post request.
Enter the Rule name and Turn it on.
To test the rule and the JEMHCloud integration, click on the "Run Rule". Revisit the Audit Logs to see if there is any problem.
Go back to JEMHCloud > Auditing > Event. The Incoming Webhook will be processed like any other issue and post function event. The email notification configuration is the one entered in the Incoming Webhook.
Click on the Report icon to view the Report
The email notifications configured in Incoming Webhook should have been sent. This is how the email looks:
...