[
https://issues.jenkins-ci.org/browse/JENKINS-12421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163010#comment-163010
]
SCM/JIRA link daemon commented on JENKINS-12421:
------------------------------------------------
Code changed in jenkins
User: Alex Earl
Path:
src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java
src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java
src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/config.jelly
src/main/webapp/help/projectConfig/presendScript.html
src/test/java/hudson/plugins/emailext/ExtendedEmailPublisherTest.java
http://jenkins-ci.org/commit/email-ext-plugin/5fa24b49277c865e63148b40d109d3df7c1a5db0
Log:
Fix JENKINS-12421
Implement pre-send script that allows modifying or cancelling the
sending of the email.
> Add pre-send step to email-ext that can modify the mail message object
> ----------------------------------------------------------------------
>
> Key: JENKINS-12421
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12421
> Project: Jenkins
> Issue Type: New Feature
> Components: claim, email-ext
> Affects Versions: current
> Environment: All
> Reporter: terryl westerhold
> Assignee: Slide-O-Mix
> Labels: claim, email-ext, feature, groovy, jenkins, plugin,
> script
>
> When the Email-Ext plugin is used in conjunction with the Claim plugin there
> is no way to configure a project's email options to only send to the one who
> has claimed it. This results in every person on a team receiving emails for
> a build they did not break, turning Jenkins emails into something annoying
> instead of something useful. For someone who knew the code this would be a
> pretty easy feature to add. And while this would be a good feature, I think
> a more elaborate solution that would allow Email-ext plugin users to
> access/modify all parts of the email message (including who the message is
> being sent to) would be more useful in the long run. Giving users access to
> all parts of the email message and the option to run a Groovy script after
> the email has been built, but before the email has been sent would satisfy
> this feature request and would make the Email-Ext plugin much more versatile.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
