Wish: tight integration with bug trackers

[GoogleCodeExporter]

It would be awesome if there were closer integration with bug trackers.  I
imagine this would behave something like how Trac updates bug tickets when
a checkin references a ticket number.  Review Board could post a update to
the bug with a link to the review request.

Trac, Bugzilla, and Google Code are all good targets for this enhancement.

Original issue reported on code.google.com by cuviper on 8 Aug 2007 at 12:03

[GoogleCodeExporter]

Original comment by chip...@gmail.com on 8 Aug 2007 at 4:11

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I have some tentative ideas for such a feature (well, a larger feature, but this
would be part of it), but there's a lot of things to consider. Someday, I hope.

Original comment by chip...@gmail.com on 8 Aug 2007 at 7:22

[GoogleCodeExporter]

Original comment by chip...@gmail.com on 11 Nov 2007 at 5:07

• Added labels: Component-Integration

[GoogleCodeExporter]

Original comment by chip...@gmail.com on 23 Dec 2007 at 7:18

• Added labels: ExtensionIdea, Milestone-Extensions

[GoogleCodeExporter]

Add a vote for this plus mention Redmine integration to the list of ticketing 
systems.

Original comment by james%lo...@gtempaccount.com on 31 May 2009 at 1:10

[GoogleCodeExporter]

I'm one of the primary developers of Bugzilla and I'm considering implementing
something along these lines within Bugzilla as a replacement for our somewhat 
aging
"PatchReader" review system. There are two ways to look at this:

1) The bug-tracker is the primary source of tracking patches.
2) Review Board is the primary source of tracking patches.

I'm coming at it from a viewpoint of #1, because:

* Bugzilla already has zillions of users and accounts in tens of thousands of
installations.

* Bugzilla has extensive email controls and most developers expect notifications
about bugs and their fixes to come exclusively from Bugzilla. 

* Responses to reviews should probably be in bug comments, because they have a 
lot to
do with fixing the bug. (This is debatable and different though, depending on 
the
team using the systems.) Thus, review comments should be bug comments.

The *minimal* system that I imagine would work something like this:

* A user can attach a patch in Bugzilla, and specify a repository (and 
optionally a
revision, if the patch is not against trunk when attached) from a drop-down 
that is
limited per-product. Possibly this information could come from review-board, 
but I'd
need some way to limit the list of repositories per-product (without having to 
set up
a separate RB instance for each product in Bugzilla).

* Add a "Code Review" button on Bugzilla's Attachment Details page. This would 
bring
up Review Board in an iframe, with the attached patch right there. It would do 
this
by creating a review request in RB and then displaying it in review mode 
immediately.

* All review requests and reviews would at first probably be performed by a 
single
"Bugzilla" user in RB, unless I could implement some way in RB to re-use 
Bugzilla
accounts.

* Once the user's review was complete, they would click "submit" in Bugzilla, 
which
would submit the review in RB (not quite sure how to do this, given browser XSS
restrictions, but I'm sure I could figure out some way), then extract the 
review as
plain text and submit it as a comment to Bugzilla with a link to the full 
"graphical"
review in RB.

Original comment by avatrax...@gmail.com on 5 Sep 2009 at 12:08

[GoogleCodeExporter]

Issue 2216 has been merged into this issue.

Original comment by trowb...@gmail.com on 3 Aug 2011 at 11:27

[GoogleCodeExporter]

Issue 2162 has been merged into this issue.

Original comment by trowb...@gmail.com on 27 Aug 2011 at 4:57

[GoogleCodeExporter]

Issue 2293 has been merged into this issue.

Original comment by trowb...@gmail.com on 17 Sep 2011 at 8:12

[GoogleCodeExporter]

Issue 2403 has been merged into this issue.

Original comment by trowb...@gmail.com on 1 Dec 2011 at 6:41

[GoogleCodeExporter]

I would love to see support for Atlassian JIRA, along the lines of the proposed 
Bugzilla integration described in Comment 6.

Original comment by jonathan...@gmail.com on 11 Apr 2012 at 12:04

[GoogleCodeExporter]

Any update on this? I'd be perfectly happy with just being able to register a 
python function that gets called as a hook on all new review posts, and 
receives (at a minimum) the branch name, description, summary, and review URL - 
fine leaving it to me to handle the rest...

Original comment by inebriec...@gmail.com on 15 Sep 2013 at 5:47

[GoogleCodeExporter]

If you'd like to do it yourself, you can do that with an extension that listens 
to the "review_request_published" signal and reads the fields from the model.

Original comment by trowb...@gmail.com on 16 Sep 2013 at 12:27

[GoogleCodeExporter]

Issue 2403 has been merged into this issue.

Original comment by trowb...@gmail.com on 25 Nov 2013 at 9:10

[GoogleCodeExporter]

I am starting to work on this issue on the Facebook Open Academy. Please post 
your ideas and feature requests on the review board newsgroup here: 
https://groups.google.com/d/msg/reviewboard/DymDgBu_9_Q/HK91wXJ4PhcJ.

Original comment by tomi.a...@gmail.com on 8 Feb 2014 at 3:05

[GoogleCodeExporter]

Here's a ReviewBoard extension I wrote to integrate with bugzilla.  I'm sure it 
would be easy to extend to other trackers.  
https://github.com/joshguffin/rboard_bugzilla

Original comment by josh.guf...@gmail.com on 3 Aug 2014 at 1:53