This support is planned for a future release (probably the 2.0 timeframe)
but doesn't exist in any way today. If you really need separation on that
level, you may have to set up multiple Review Board servers.
If they already have access to the sourcecode on other repositories/groups
anyway, and it's just about enforcing a policy about them
commenting/reviewing someone else's code, then the best solution today is to
just make it clear that they're not allowed to do that.
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Tue, Dec 15, 2009 at 7:10 PM, JohnHenry <qhlonl...@163.com> wrote:
> Hi, all.
> There is a new request for us. In ReviewBoard, each person has an
> "All review requests" on his WebUI so that he can make commentment to
> all ReviewRequests. But some times we don't want some user to make
> comment on the project he didnot attend. Or we even did not want him
> to see the review requests in the ReviewGroup which he is not in.
> Anyway, We need more detailed and powerful permission control on
> ReviewGroups. How to realize those functions then?
> Best Regards!
> Want to help the Review Board project? Donate today at
> Happy user? Let us know at http://www.reviewboard.org/users/
> To unsubscribe from this group, send email to
> For more options, visit this group at
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at