By default on most permission schemes, the reporter is set to be notified of events such as Issue Assigned. Hence the new reporter will get an email notification provided your notification scheme is set to notify the reporter on that event. When you are changing the reporter of an issue, the new reporter is expected to be notified if your notification scheme has reporter listed in that Issue Assigned event.
Adding, editing, and deleting notification schemes has an overview of how you can set this up or check to make sure that your current notification scheme is setup this way.
You are completely correct. I made a mistake in my previous reply. I have confused the reporter and assignee in this case.
The notification event that you would want to use would instead be "Issue Updated". In order to change the reporter on an existing issue, you have to edit the issue to do so. In that case when you update the reporter field, the new reporter would be expected to get a notification, provided that Reporter is setup to be notified of issue edits.
Sorry for the confusion of my previous reply. I hope this helps.
Thanks Andrew, no worries at all. I have also seen that, however we only want the notification to be sent out when the Reporter field is edited, not any of the others. The reporters are being spammed with issues being edited which is an issue hence why we want it to be restricted to one field.
Hey Atlassian community, I am a PM on the Bitbucket Cloud team and I am excited to share that we just released an improvement to the Jira Software and Bitbucket Cloud integration. With the newly im...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs