It's all about the answers!

Ask a question

ad-hoc report


Gary Dang (59328552) | asked Apr 01 '08, 8:39 a.m.
One aspect I think Jazz could improve is about Reports. I think that the project manager o the admin user should can build ad-hoc reports using different information in repository (work items, changes, ). Is there a way to do this?

One answer



permanent link
James Moody (3.3k24) | answered Apr 01 '08, 8:39 a.m.
JAZZ DEVELOPER
gdang wrote:
One aspect I think Jazz could improve is about Reports. I think that
the project manager o the admin user should can build ad-hoc reports
using different information in repository (work items, changes, ).
Is there a way to do this?


Hi Gary,

This is indeed possible today. I'm not sure exactly which data you're
talking about so let me divide the problem in two:

1. Historical data. Jazz takes regular snapshot of information about
many different artifact types and aggregates this information into a
data warehouse. Most of the reports we ship out-of-the-box operate on
this data.

2. Non-historical data about artifacts in the repository right now. We
have a couple of reports that work like this: take a look at "Work Items
by Owner" and "Work Items by Team Area" in the "live/" folder of
com.ibm.team.examples.reports.common if you want to see how these work.

For each of these cases, we've implemented some data sources that BIRT
can consume. The historical ones operate on the data in our data
warehouse; the live ones operate on the query model for different
component types. After 1.0, we hope to make the support for the live
data sources even more generic.

If you're interested, I encourage you to try out our tutorial on
building a new report. You can find it on the Reports wiki here:

https://jazz.net/wiki/bin/view/Main/ReportsCreatingANewReport

It's mostly up-to-date but will need some tweaks when M6 is delivered.

Having said that, our focus for RTC 1.0/Jazz 0.6 has been on
consumability of reports as a whole by end users, and on our
out-of-the-box reports specifically. In particular, for a casual user
who isn't familiar with BIRT, it can be a bit daunting - it's very
powerful but has a bit of a learning curve; this is one of the reasons
we don't yet promote this path as a first-class activity for end-users.
After 1.0, one of our priorities will be to investigate ways to make the
*authoring* of new reports easier for end-users who are so inclined.

Thanks for the comments.

james
Jazz Reports Team Lead

Your answer


Register or to post your answer.