You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Jake Farrell (JIRA)" <ji...@apache.org> on 2014/06/26 21:55:24 UTC
[jira] [Commented] (INFRA-7971) Modify notification behavior for
MESOS
[ https://issues.apache.org/jira/browse/INFRA-7971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14045072#comment-14045072 ]
Jake Farrell commented on INFRA-7971:
-------------------------------------
1. issues@mesos.apache.org requested (you can request mailing lists using [1] )
2. once the req is processed i'll switch jira notifications over
will provide more details on the other requests once the 1 & 2 are done
[1]: https://infra.apache.org/officers/mlreq
> Modify notification behavior for MESOS
> --------------------------------------
>
> Key: INFRA-7971
> URL: https://issues.apache.org/jira/browse/INFRA-7971
> Project: Infrastructure
> Issue Type: Improvement
> Components: JIRA
> Reporter: Chris Lambert
> Assignee: Jake Farrell
>
> We'd like to make a minor change to how email notifications are handled for the MESOS project.
> # Create a new email list called issues@mesos.apache.org
> # Re-direct all email notifications to this new email address
> # Modify the "from" header to not include the actual name of the person, instead replacing it with something generic like "Apache JIRA".
> #* This is because in thread view, only the name of the ticket creator ever shows up, which is misleading since often notifications come from other people.
> Also, we'd like to be able to automatically subscribe the dev@ list to a saved filter so that we could, say, send a weekly status message to dev@ of all the tickets that had been updated that week. I'm not sure how to do this, or if it can be done, though. Can you advise?
> The whole goal here is to increase the signal to noise ratio on dev@.
> Thanks.
> /cc [~benjaminhindman], [~jfarrell]
--
This message was sent by Atlassian JIRA
(v6.2#6252)