Matrix builds file one comment per sub-build. In large matrices this becomes
unbelievably noisy.

In addition to polluting the history of the issue, one email is sent per
comment. This also quickly raises the ire of users.

The Marvelution hudson-jira plugin is great but does not provide long-term
accountability. One of the advantages of this plugin is that the comments by
hudson are permanent records.

Suggested workaround:

• turning it off and losing that accountability;
• creating a mail user agent filter which marks such emails as read, and files
  them in a special folder or even deletes them. (by each user, for each user,
  undesirable, unmaintainable)
• a non-resolved improvement on atlassian's site to permit a comment as a "minor
  change", ala confluence's button, buying an upgrade license and minor change to
  the plugin - [JRA-2410 Add checkbox " Minor changes , don't notify" to
  coments ...|http://jira.atlassian.com/browse/JRA-2410] (sic)
• hacking the hudson plugin
  • to re-edit existing comments rather than posting new ones (which may still
    email users - but cleans up the history);
  • wait until matrix builds are complete and report the ultimate solution

I am running Jira 3.13.3, Hudson build 320.