8 years later....Any hope on the horizon???

Please add this feature because it will lower the frustration and blood pressure for every JIRA user.
//Johan

The absence of this feature is a major impediment to us getting more projects to use JIRA. In our current and past projects over several years, many people complain long and bitterly about the email spam they get due to us (the process managers) and other people making changes that nobody else needs email about. We use JIRA largely because it helps us use agile methods even on large, complex projects, which requires us to make lots of changes frequently. For example, often we move large numbers of issues back and forth between sprints, dot releases, or even major releases as we reprioritize multiple times per day, but nobody on the team needs to or should get emails about all those moves. Usually we need to do that one issue at a time, because we need to open each issue to look at all its attributes before deciding what to do with it. We have lots of watchers on most issues, because of the interrelatedness of the team members' expertises and work assignments, so each change email-spams lots of people.

Please think about this one. This one minor ommission makes JIRA unsuitable for many uses, which is a shame. It renders the e-mail notifications almost pointless, looks unprofessional to clients, and many receivers soon implement a mail filter to skim off all JIRA mails.

The current workaround is to require admin rights and do a bulk update of a single issue, unchecking the "notify" box. This shows that the basic functionality already exists in the system, so I expect this is not a major change. If this is a security consideration then surely just adding the option for administrators, or with a new permission group would be a start. Using the bulk update work-around requires making most users admins, and is too cumbersome for an agile development team.

Confluence has this feature, why not Jira? It shouldn't be complicated to implement it - just include a template in appropriate issue view JSPs, perform an additional check in the Actions and add (or edit) a method to the needed Services.

We have it in the following places:

• Logging work:
  • Issue view -> More actions -> Log Work
  • Issue view -> Issue tab Work Log -> edit/delete existing worklog
  • Issue navigator -> the last column in issue view, click on the gear icon and choose Log Work
• Issue operations from either Issue view or Issue Navigator and when choosing Actions:
  • Edit Issue
  • Add Attachment
  • Link Issue
  • Assign Issue
  • Add Comment (either by pressing Comment button on the top or bottom of the Issue View screen)

Instead of maintaining the code ourselves across all Jira releases, we would like to see it in Jira itself. Maybe we could even help with sharing the code if the need be..

We have this actually implemented in our instance and can't imagine the life without it.

Atlassian guys, do you have any plans to add this feature? More than 3 years have already passed...