I have integrated RB with our bug tracker, a heavily customized version of
GNATS. I modified the RBBugTracker extension published by a student, I
believe, a few years back.
That extension was built for google code, though the extension has a
plug-in architecture so I added one for GNATS. It wasn't too much work to
port to the latest RB version. Mostly the init() functions needed some
tweaking - an extra argument as I recall.
The framework for trapping the relevant signals was already there, as well
as a simple admin panel. I found it fairly simple to add a class for our
bug tracker with a method to process the signals. Upon receipt of a signal
I chose to simply exec existing scripts to modify the bug tracker. If you
have a native Python API to your bug tracker you could go that way I
While this extension has been quite useful with RB 1.7.x, it will be even
more useful with RB 2.0. The main reason is that you end up needing to
communicate meta-data between the front-end (rbt post) and the back end
(the bug tracker extension). Right now I do that with change descriptions
but it's a little hacky.
I've not yet written a UI extension to display bug info in RB, though that
would be desirable.
I've emailed at length with Christian, who's been a tremendous help, of
course. If it helps I can help explain the modifications in more detail,
and I'm hoping to publish the code diffs.
On Friday, February 7, 2014 6:07:54 PM UTC-8, Tomi Äijö wrote:
> My name is Tomi Äijö. I am attending the Facebook Open Academy this spring
> contributing to Review board. My student project has to do with Review
> board bug tracker integration (see issue
> I would like to hear ideas and feature requests from the community
> regarding this project. I have been looking into the following bug trackers
> so far:
> Google code: No public API any more (
> JIRA: Public API (https://bitbucket.org/bspeakmon/jira-python)
> Trac: No officially supported API, there exists a plugin called
> XmlRpcPlugin that provides API but not actively maintained (
> Bugzilla: Native XMLRPC interface (
> Reading the issue 193 and its duplicates the following features seems to
> be the most desired:
> - Posting a comment when a review request is linked to a bug
> - Change the status of a bug according to the corresponding review request
> - Show information about the bug in Review board
> Please share any ideas and comments regarding to this project!
> Best regards,
> Tomi Äijö
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
Happy user? Let us know at http://www.reviewboard.org/users/
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/groups/opt_out.