The issues feature is actually meant to replace having to say "OK" or
"Fixed." It's just a way of saying, "This needs to be done" and for the
other person to respond saying "It's done!"
Going forward, we're building on this through the introduction of an issue
summary table in 1.7 (which shows what issues are still pending, so you
have a To Do list of sorts), and we'll also be showing the fixed issues on
every diff update.
Now, we're also introducing a per-user option to default that Open An Issue
checkbox to unchecked for new comments. There's no site-wide default, but I
suppose that could be added.
Still, I think issues actually integrates into your workflow even nicer.
Just open the issues, and instead of "OK," hit "Fixed." The effect is the
same, but you'll gain some benefits going forward.
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Sep 5, 2012 at 12:58 PM, J Arrizza <cppge...@gmail.com> wrote:
> We need a positive way to indicate that a review was done. Currently we
> use a manual process of adding an "OK" comment to each code review by each
> reviewer. When all comments are "OK", then we know the review passed.
> This process worked ok in 1.0.7 but fails for us in the current version
> because the new "issues" feature now flags every comment as an "issue"
> when, in our case, they are not.
> So a couple of questions:
> 1) is there a way to turn off the "issues" feature?
> 2) is there a way to have the "issues" feature exclude comments with a
> given pattern e.g. /^OK$/i ?
> 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