If the notification assistant has stopped sending notifications, it may be due to several reasons. Look into the following action points to get the issue resolved:
Searches happen in the context of a user. Depending on how your permissions are configured, you may need to configure an Executing User. If a notification is not sending:
Make sure that you only have a single Event firing in your Transition's Post Functions
Your Template has a set of configured fields:
But the email you get has more fields that expected:
Notification Assistant for Jira 6.4 added support for showing changes in notifications with a Time based trigger. You can disable it by editing the Template and unchecking the Include Field Changes option.
You have provided an email like fake@example.com to be notified. However, the user is not getting notifications. Or you have had a notification with this configuration, and it suddenly stopped working.
Check your users and see if anyone has this email assigned to them. If they do, and their account is disabled, then Jira will not email them.
Job | Description |
---|---|
com.riadalabs.jira.plugins.notificationassistant.InitNotificationAssistantJobImpl | This job should only run once, and successfully |
com.riadalabs.jira.plugins.notificationassistant.NotificationAssistantJobImpl | This job is the scheduling job and should have one job for each notification that uses scheduled triggering. Look into if everything has been executed okay with no errors. If errors look into the atlassian-jira.log for traces. |
com.riadalabs.jira.plugins.notificationassistant.EventAssistantJobImpl | This job is the event handler job and should have one job for each notification that uses event triggering. Look into if everything has been executed okay with no errors. If errors look into the atlassian-jira.log for traces. |
Enable additional logging in Administration > System > Troubleshooting and Support > Logging and Profiling by setting the following to DEBUG to see more robust logging about services running at the background
:
com.atlassian.jira.service
com.atlassian.jira.service.services.DebugService
Make sure that you can connect to the Slack web hook from your Jira server
curl -X POST -H 'Content-type: application/json' --data '{"text":"Testing"}' https://hooks.slack.com/services/<EXAMPLE> |
If Jira connects to the internet via an outbound proxy like so
-Dhttp.proxyHost=proxy.example.org -Dhttp.proxyPort=8080 -Dhttps.proxyHost=proxy.example.org -Dhttps.proxyPort=8080 -Dhttp.nonProxyHosts=localhost |
Then you can also test using the proxy from the command line as well
curl -X POST -H 'Content-type: application/json' -x <proxyUser>:<proxyPassword>@<proxyHost>:<proxyPort> --data '{"text":"Test"}' https://hooks.slack.com/services/<EXAMPLE> |
See the instructions at Capture and Provide Logs