I think this is also a useful suggestion for ticket-based Tracs as well. Thinking of Tracs like fedora-commops, fedora-diversity, and soon-to-be fedora-marketing, it would be helpful if new tickets sent emails to a mailing list (I think new comments, edits, tagging, etc. would be too noisy).

Having an option to choose what content of an issue is emailed would also be super helpful!

So I would need a little more info on what to send:

• Every (public) notifications as you have now when you watch a project?
• Just new tickets?
• New tickets and comments?
• New tickets and new PRs?

@jflory7 I am not sure we want to go to the level of granularity where you can specify multiple address each having different notifications settings. I am more inclined to allow a list of emails to be notified based on a certain policy.

I think new tickets and comments are useful for mailing list but not PRs, let the individual watch the project which will send PR information to that individual user.

I am not sure why any project need to send updates to multiple emails/mailing lists.

I think new tickets and comments are useful for mailing list but not PRs, let the individual watch the project which will send PR information to that individual user.

Works for me :)

I am not sure why any project need to send updates to multiple emails/mailing lists.

Not sure either, but it's easy enough to split the input by commas.

@pingou To clarify my earlier comment, I think what would be most useful from my perspective is new tickets and new comments sent as notifications to a mailing list specified for any given repository.

Originally, I was referring to having the option to choose what notifications are sent (e.g. an email for new issue, new comment, edited tags, etc.), but now I think that might be too specific. Just notifications for new tickets and new comments should be sufficient, I think.

Commit 080c159 fixes this issue