Forum OpenACS Development: Bug Tracker Aggregator

Collapse
Posted by Roberto Mello on
Hi All,

In dotWRK we are in need of aggregating bugs/tickets from several bug-tracker projects/instances to be shown in a community portlet.

So I was going to create a bug-tracker-aggregator package, but my current idea is to just modify bug-tracker in the following manner:

1) Add a IsAggregatorP parameter
2) In the index page, if it's an aggregator, redirect to a different template that will show the bugs/tickets for all BTs mounted under it.

Ideally we would have an aggregator instance of BT be able to aggregate from BTs mounted anywhere, but I need this done very soon and it can be improved later.

Comments/suggestions welcome.

-Roberto

Collapse
2: Re: Bug Tracker Aggregator (response to 1)
Posted by Lars Pind on
This is very similar to what we do in Logger, though we do it more explicitly.

Logger package instances and logger projects are independent, and are linked with a mapping table.

The way we use it internally is this:

Mounted at our intranet, we have a logger instance, which is mapped to all projects in the system.

Mounted at each of our client extranets is a logger instance, which is mapped to the projects involving that particular client.

I could see the use of a similar model for bug-tracker.

/Lars