# Skipped Emails

The server will try to minimize redundant emails, which are notifications to the user that just made a change. Emails will be tagged as "skipped" if the email address for a notification to the email address in the profile for the user that is currently making a change.
This can make testing of notifications with a common email address more difficult as the system may see a common email and suppress the notification, if the email matches the user profile for the current user. A user can turn this off with the "Send Redundant Notifications" setting in their user profile email preferences.

# Missing Emails

After a change is made, the user will see a list of notification details at the top of the resulting details page, assuming the smtp server settings are set up correctly.

If one of these email addresses in the "Notified:" area is not getting an email, please try the following :

- check the spam folder of the user's email client
- look at the exception log for the FIT server for any email errors (Admin->Advanced->Exception Log)
- consult the IT department responsible for the email address to make sure it is not blocking emails, as it may need some configuration to accept continuous emails from our server.

# Notification Rules

Email Notification is the process of sending an email to a related party for the purpose of keeping them up to date on a current issue. On any update to the system, the default behaviour of ATS is to send a notification to the user who is currently assigned to the modified issue. The one exception to this rule is if the person who is making the changes is actually also the assignee. In this case, there is no need to send a redundant email about information just entered by the same individual.

In addition, several notify lists can be used to direct notifications:

- Each issue includes a separate Notify List, which contains additional email addresses and/or users, who would like to remain informed as to any changes to a given issue. The contents of this list remain intact throughout the life of an issue, until they are manually removed.
- Filters can be saved with a Notify List which directs a notification to users any time an issue is saved and matches the associated saved filter.
- Mail Rules can contain notify lists for bug creation when using anonymous email retrieval.
- Workflow Actions have a notify list option if using workflow rules.

The system keeps track of where to send an issue, using the email address associated with that user, in their configurable profile. This address can actually include multiple addresses, if they are separated by a comma or semi-colon. When a bug is modified, the system creates an email notification and directs it to a list which contains the following:

- A. All email addresses in the assignee profile
- B. Any addresses in the Notify Lists (defined above)
- C. Any addresses contained in the profiles for any users in the Notify Lists

This list is automatically stripped of duplicates and/or a matching assignee email address (which avoids the redundancy problem outlined above). All notification is accomplished using a SMTP server, as configured in the Server Configuration menu of the Admin section.