Summary

• Email notification is sent to user who is assigned to an issue using post function although the fire event is not associated to any email ( user or group ) .

Steps to Reproduce

1. Create a dummy event ( No eMail)
   
2. Create a new Notification scheme and only configure the following :
   
3. Associate that notification scheme to the project.
4. Edit the project's workflow to have a looped transition back to the same state, add a post function event for Update Issue Field and then Select the Assignee field to be assigned with a user (Test) then click Add.
   
5. Edit the Fire a Generic Event event that can be processed by the listeners. with the new event created earlier (No eMail)
   
6. Publish the workflow.
7. Create an issue without an assignee
   
8. Transition the issue to the same state and the issue will be assigned to the user configured in the post function ( Test ).

Expected Results

• Email notificaiton is not supposed to be sent to the assignee ( Test ) as the post workflow is not firing the issue assignee notification but a dummy event ( No eMail )

Actual Results

• Email notification is sent to the assignee ( test )
  

Notes

The expectation from previous version 5.2.11 is NOT to receive an email since the event "No eMail" hasn't any recipients in the notification scheme. This event was created to make sure there are no emails sent during the transition.

Workaround

• Remove the notification of Current Assignee for Issue Assigned (System) for the project's notification scheme. This will completely prevent the Issues Assigned notification from being fired.
• Instead of using Current Assignee for the Issue Assigned (System) notification, you can associated it to a Group. You can associate members who you want to receive notification if they are assigned to an issue. If the user is not in that group, the user will not receive any notification when assigned to an issue.