Q:

Aggregator tool for multiple heterogeneous bug/issue trackers?

I do software development with a team as a part of my graduate research. We are involved in a number of projects hosted in various places: some on public GitHub projects, some on a private Redmine instance, etc. Some logical projects are split into multiple project repositories, often with some public parts and some private parts. We're using the issue tracker for each project for its respective hosting location, which is good except that we now have a lot of places to check and I'm worried we're approaching "tool overload" - too many places to report a bug, too many places to check for bug reports.
So, the question is: Is there an aggregator tool/web app that we could configure to show us at least a combined bug list from multiple different bug trackers? It would be nice if it could also show a combined "activity feed" (as both GitHub and Redmine offer), and even better if we could add 'one-off' external bugs to track (something in an upstream bugzilla, for instance) but now I'm really getting into dreamland.
"Me too" update 2013-02-14:
I was going to post a question which is clearly a duplicate of this.  Since it's not got an accepted answer (and neither of the answers seem particularly satisfactory), I'll extend this one:
I'm dealing with multiple teams (over multiple sites) each using different issue trackers (all of Redmine, Jira, FogBugz and Trac of interest currently).  I have web access to the trackers and the issues in which I'm interested in each tracker are generally quite good about cross referencing related issues in other trackers (ideally in a custom field).
Are there any tools out there which will somehow present a more unified view of a particular project effectively spread across multiple teams than I'm getting at the moment from having multiple browser windows opened?
An example of the sort of workflow I'm trying to improve would be spotting issues that one team claim to have fixed but the downstream dependent team need prodding to pick it up and validate it, or spotting when downstream have decided something isn't needed any more but not notified the upstream.
Note that processes, policies and politics are such that there is no hope everyone will agree to use one common tracker somewhere.

A:

I don't know of any ready-to-run aggregator tools, but you should be able to use Ticketmaster to build your own as it provides a consistent interface into various providers including github and redmine.

