There's no support for that today. This is less an issue thing and more a
comment thing. We tie issues to comments, and comments to some part of a
file/diff. The exception being that you can leave a general summary comment on
a review, but that works differently internally and making it work in such a
way where multiple issues could be filed would be a rather large change.
I'm not sure what the best solution would be for your needs right now. Any
solution would involve conceiving of and implementing a new design.
On Dec 7, 2012, at 11:52 AM, Matthew Woehlke <mwoehlke.fl...@gmail.com> wrote:
> Is it possible to create an issue for a review request without it being
> associated with a code comment? (I don't see a way, but want to check if I'm
> missing something before filing an enhancement request.)
> The use case I am thinking of is that I go to test a patch and discover that
> it has e.g. introduced a behavioral regression, but don't know what specific
> code is the culprit. I think it makes sense for tracking purposes to be able
> to open an issue describing the problem, rather than just a review stating
> that a problem exists.
> 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