[ 
https://issues.jenkins-ci.org/browse/JENKINS-12421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162884#comment-162884
 ] 

terryl westerhold commented on JENKINS-12421:
---------------------------------------------

Yes, that is what I was thinking.  I am curious to know how you are thinking 
you will approach this issue though.  Having a feature that specifically 
addressed the claim issue would be great, but I really think the "more 
elaborate solution" I mentioned in my initial post would be much more 
beneficial.  Giving the option to run a "pre-send" script after the message was 
fully built would give me the ability to fix this issue, and the potential to 
do many other things with the MimeMessage before it was sent.
                
> 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

        

Reply via email to