issue identifying trigger for notifications

[Daniel Eliades]

We have reports from some users saying they are recieving emails for ticket creation and modification that are outside of their department, and when we run the notification checker, no matter the criteria, it suggests they should not be recieving these emails.

The user believes it is related to the groups being reported under their user profile information, which lists all currently created AD groups, despite the AD groups not being assigned to them, not being removable, and only a few projects of what would be many creating notification emails for her. I think these are two unrelated issues, or indirectly related issues.

I would love suggestions on where to look, however we have some abnormal restrictions on our environment that block some logging features that we cannot enable, so please feel free to suggest, but not everything can be implemented when it comes to some of the logging features.

[Brant Schroeder]

Daniel,

  I would do the following:

1. Have them forward a couple of the emails that they received.
2. Once you have the emails you will be able to see what they project is and the issue in that project that they received the email from.   
3. Check the issues and see if they are on the issue as the reporter or a watcher.  If they are not one of those and this is a Jira Server issue and not a Jira Service Desk issue then they should not be getting an email.
4. Check the project and see if they are associated with it in any way.  Check the users and roles first to see if they exist there or if one of the groups they are associated with exists there.  If their user or a group Their user exists in is there then they will be able to receive notifications.  
5. If they can receive notifications but are not on the issue you will need to make sure that there is not workflow process that sends notifications.  You should also make sure that there are not any apps like Automation for Jira that could be sending the update.  
6. If all of that fails and you can not find where the notification is coming from you should make sure that there is not an account on the issue that is sending the email.  We have had email lists in the past that have been setup as users on the instance that forward emails to users.
7. You can also use a tool like splunk to trace the email if you have it.

Let me know what you find out.

[Daniel Eliades]

They are not reporter or watcher (or assigned)

They are not associated to the project in any way

you mean that a step in the workflow would automatically generate the email (so like a group or an individual) like a post process?

automation for jira is an add-on, right?

how can I check for an associated email list?

[Brant Schroeder]

Daniel,

  Have they sent you an email yet?  Do you have anything like Splunk that you can review network activity in.  

Automation is an add-on.

What reporter and watchers are on the issue?  I would check those to make sure that they are user accounts and not a distribution list.  

Also this is a Jira project and not a Jira Service Desk project correct?