Is their a way so that people can control, in a fine grained maner, when they get emails for: - new review requests - new reviews - updates to review requests - comments on reviews
We might be able to do that down the road, but not for 1.0.
- Type-Defect + Type-Enhancement + Component-EMail + Milestone-Release2.0
Adding more info - Wikipedia sends an email once, but then stops sending email until the user has signed in and looked at the changes. This would be a nice option. More often than not I'm bulk deleting 15 reviewboard emails because it spams me so much. Perhaps a digest could be sent out once every 15 minutes or something?
One stupid little thing is that the author of any change receives an email, too (at least when he is a member of the target group). There is not many annoying things worse than following your own changes.-) > Wikipedia sends an email once, but then stops sending email until > the user has signed in and looked at the changes. this sounds very reasonably, too I'd be glad to see at least some little enhancements before 2.0, since it seems to me that the mailing (spamming) is the biggest shortcoming in 1.0. (A great tool anyway, thanks!)
Reviewboard could become a little noisy depending on usage patterns. I think some controlls would be usefull: * send notifications to groups / not (this would probably allow to use groups for selecting / grouping bugs) * bcc me on my own Publish events / not * or something like "just mail me if I'm assigned a review" If a team-"manager" is to track and distribute reviews, RB currently doesn't offer a good way here; Maybe the User ACL thing could be a good place to configure/store this?
I don't even think there needs to be an *option* for "send me email on my own Publish events" -- it's just spam, plain and simple. Perhaps we could separate this smaller request out from the larger topic of "email control", and address it sooner?
This probably depends on whether or not you're using mailing lists. In the case of a mailing list, you want an e-mail going to the list, and in most cases that implies going to yourself anyway. Perhaps we should disable e-mails to yourself when you aren't using mailing lists. However, I don't know that it's really black and white. I personally like to have a thread I can read in my e-mail client with a good starting point, rather than a bunch of reviews with no parent e-mail. If using mailing lists, a per-user option wouldn't apply anyway, but otherwise, having a checkbox in your account settings for controlling this would be, in my opinion, an important thing to have when addressing this request.
Another thought: Every bug tracker I've used has sent me an e-mail when I file a bug. That's not much different from what Review Board does. Do people have the same complaints there, and is there something people are doing to address that?
Ok I cede the control issue, and have no problem with other people getting as much mail as they want. No good threading here (cough corporate Outlook cough), so it's painful. We're a Fogbugz shop, and it (thankfully, to my thinking) does assume that it doesn't need to tell you what you just did.
I disable that feature in every bug tracker I use. Besides, just because every other X does something doesn't make it good usability. Every email takes at least a few seconds to process, and it quickly adds up. However, if you really don't want to implement this feature, people can set up a filter that automatically throws these emails in the trash. The downside is that it's a client-side filter, so it has to be set up on every client you read your mail from.
well, got the same issue: my team members are annoying that they receive "spam" when they commit any changes to SVN (because the letter "Review Request" is pointless for them, I'm the only guy, as a reviewer, interesting to know that request is generated). Would be nice at least to have appropriate option to control it. Also just yesterday or a day before I added a comment to another issue #2050 : I am a default reviewer, but only for java files. My dashboard works well (I see only requests with java changes), but I get a "Review Request" mail for every single commit (flex, sql, configs...). It would be great to have better control over this issue, to configure mails appropriate
In addition to the fine-grained control, I'd like email notifications to be sent (optionally) on issues being dropped, fixed, or reopened. The email should be sent to parties commenting on the issue other than oneself. Also, on the fine grained control, it would be nice for the admin to configure default values for the users. Users should then configure what they want to see as there might be an interest for an author to see more or less email than a reviewer. So, two notification profiles might be needed per user.