Thanks for taking the time to raise this issue.

Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts. In part, that means concentrating on those issues that resonate the most with our users.

I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue.

Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me.

Kind Regards,
Kerrod Williams
JIRA Product Management
kerrod.williams at atlassian dot com

Would like to give support for Marc Tamsky's solution. This would go a very long way, especially now that we are also using Jira Service Desk - this feature is very common in helpdesk solutions, but we have just as much spam in our Jira projects. Hopefully we can get folks voting on this functionality to give the commenter control. I was just about ready to submit a new ticket with the following text.

As a Jira or Jira Service Desk user, I would like the ability to disable sending emails to all watchers on a ticket when adding a comment. This might be accomplished through the use of a checkbox in the "Add Comment" dialog or perhaps could be an additional button next to the Add button titled something like "Add No-Notify" If checkbox, default should be enabled to mimic existing functionality.

Business value/justification - email communication is very noisy for actively commented tickets that have several watchers. This functionality would provide the commenter the ability to reduce the email noise while adding relevant information to the ticket for future use or to capture thoughts.

Can we start with having a disable checkbox for single operations, like Add Comment?

Please add a checkbox to comment form fields:
<Add> <Cancel> <X> Do not send email for this change

Thanks!

(following on from previous (B)) Add a JIRA role of Assistant.

from Bulk operation update

Disabling Mail Notification for Bulk Operations

It is possible to disable mail notification for a particular bulk operation by de-selecting the 'Send Notification' check-box in the bulk operation wizard. In order for this option to be available, you must be an administrator or project administrator of all the associated projects on whose issues the bulk operation is being performed.

I doubt I would get Admin rights to all projects that work on (and I don't own) - I wouldn't even want that - BUT, I would like to be able to do BULK updates, that DON'T disturb 'the balance of the force' - creating noise for engineering. test teams etc.

(End-User option...)

A) Would it be possible to limit in this way (or something similar):

• Limit Comment Event emailed out within a 10 minute threshold:
  • if a new/updated comment event has already been sent out - an event sent to email out a notification email of the JIRA
  • - and JIRA then the same JIRA is updated within a configured threshold (e.g. 10 minutes) then no notification is sent out for the Edit (& more changes within the threshold).

B) Alternatively - extend some of this functionality to those users who:

• CAN perform bulk updates
• ARE NOT Administrators or Project Administrator

As don't believe this is available to that group at them moment

Disabling Mail Notification for Bulk Operations

It is possible to disable mail notification for a particular bulk operation by de-selecting the 'Send Notification' check-box in the bulk operation wizard. In order for this option to be available, you must be an administrator or project administrator of all the associated projects on whose issues the bulk operation is being performed.

Thanks for submitting this request -

We hear similar things from other customers about reducing email volume, and comments seems like a good area for attention. I'm going to co-opt this issue and broaden it to encompass multiple ways to reduce comment emails.

Options here might also include the ability to limit the number of comment emails, or even a digest-like option for users who don't want to see every comment email.

Bryan Rollins
Product Manager, JIRA
brollins at atlassian dot com

So before any mail is sent by the mail service, check if the mail was for a Issue Commented or Updated event. If not, send it. Else get the issue id, comment id and date of change. Check the given issue and comment id for an update since the date of change and don't send the email. The other event will cause a notification.

I'm not sure that this happens all that often, but anything to reduce JIRA spam in large systems is good.