Comment #27 on issue 477 by 0711...@gmail.com: Per reviewer email control
https://code.google.com/p/reviewboard/issues/detail?id=477
Seeing 'Labels: -Milestone-Release2.0'. How can we separate email
notification between new request and every reviews?
Sometimes we do not need to know every
Comment #23 on issue 477 by trowb...@gmail.com: Per reviewer email control
http://code.google.com/p/reviewboard/issues/detail?id=477
Issue 2534 has been merged into this issue.
--
You received this message because this project is configured to send all
issue notifications to this address.
Comment #24 on issue 477 by trowb...@gmail.com: Per reviewer email control
http://code.google.com/p/reviewboard/issues/detail?id=477
Issue 3051 has been merged into this issue.
--
You received this message because this project is configured to send all
issue notifications to this address.
Comment #22 on issue 477 by plevn...@gmail.com: Per reviewer email control
http://code.google.com/p/reviewboard/issues/detail?id=477
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
Comment #19 on issue 477 by earthl...@gmail.com: Per reviewer email control
http://code.google.com/p/reviewboard/issues/detail?id=477
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
Comment #18 on issue 477 by trowb...@gmail.com: Per reviewer email control
http://code.google.com/p/reviewboard/issues/detail?id=477
Issue 2316 has been merged into this issue.
--
You received this message because you are subscribed to the Google Groups
reviewboard-issues group.
To post to
Comment #17 on issue 477 by james.a.baker: Per reviewer email control
http://code.google.com/p/reviewboard/issues/detail?id=477
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
Comment #15 on issue 477 by chipx86: Per reviewer email control
http://code.google.com/p/reviewboard/issues/detail?id=477
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
Comment #16 on issue 477 by chipx86: Per reviewer email control
http://code.google.com/p/reviewboard/issues/detail?id=477
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
Comment #13 on issue 477 by trowbrds: Per reviewer email control
http://code.google.com/p/reviewboard/issues/detail?id=477
Issue 1214 has been merged into this issue.
--
You received this message because you are subscribed to the Google Groups
reviewboard-issues group.
To post to this group,
Comment #10 on issue 477 by o3sisqa: Per reviewer email control
http://code.google.com/p/reviewboard/issues/detail?id=477
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
Comment #9 on issue 477 by premek.paska: Per reviewer email control
http://code.google.com/p/reviewboard/issues/detail?id=477
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
Comment #8 on issue 477 by trowbrds: Per reviewer email control
http://code.google.com/p/reviewboard/issues/detail?id=477
Issue 1146 has been merged into this issue.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
13 matches
Mail list logo
