Guuuuuys, is it so hard to implement such a feature?

I couldn't agree more. It's so straightforward to implement. Yet, 12 years later, we still have to set up and maintain a Postfix server just to filter out the emails sent by JIRA, and pay thousands of Euros to Atlassian every year. Very sad.

https://jira.atlassian.com/browse/JRA-1369 says "we will not be addressing this feature in the next 12 months", with a few other links.

Clearer communication about what is and is not going to be implemented on this front would go a long way.

Many thanks for your votes and feedback on this issue. While have no plans of addressing this in the near future, we do plan to address https://jira.atlassian.com/browse/JRA-1369, which should alleviate some of the pain you're describing.

Thanks for your patience, and we hope you appreciate our open approach to feature requests.

Kind regards
Tom Kotecki
JIRA Product Manager

Guuuuuys, is it so hard to implement such a feature?
We use JIRA heavily, so have a lot of requests just to turn off notifications as those users just delete all the "spam".
Also, we can't change email address for the user as use AD as User Directory.

I second Eddie Webb. This is particularly an issue since the only way to do API integrations is to set up a dedicated username and password. That user has to have an e-mail address, and so it'd be a significant help to not have it receive e-mails whenever users comment on stories the API creates.

This would be vry useful to us for a different reason. We use the default system "administrator" account for tickets created by email and issue collectors. But the account has a Districution List tied to it, and our mailbox gets spammed with any change to all tickets where the admin ID is the reporter. (the notification schemes are perfectly valid as most cases the reporter is a human ID)

Another use case: Sometimes you have accounts set up for use by automated systems to create and edit JIRA issues. You don't want e-mail notifications to be sent to them.

I have the exact same use case as described in JRA-22175, which is linked as a duplicate of this ticket. Would really like to be able to disable notifications for a robot account that still needs to remain active since it creates tickets via email and the API.

Being able to opt-out of all e-mail notifications would be useful to us, and since Jira can be configured to auto-create user accounts based on an email-triggered ticket creation, it may be necessary for regulatory compliance, as well: http://en.wikipedia.org/wiki/CAN-SPAM_Act_of_2003

since Jira has RSS feeds now, some of my users perfer getting informed that way vs email so having a choice to not force everyone to get email is of value. Since some users want email I cant just disable the emails altogether. It definitely needs to be a case by case (ie user by user) basis.