pawrampe wrote:

Team members would like to know, If we implement RTC, how will this
help our traceability and auditing across the lifecycle". They
do this today through spreadsheets and word documents. Sure you can
go to one WI and see what it's linked to, but what they are looking
for is a traceability report that looks or achieves something like
this....

Story work item 20
|
-----> Software Requirement work item 24
|
-------> Activity 104
|
-----> Change Set
|
-----> These files...

Does anyone have experience in creating this BIRT report/view from the
data in Jazz?

Hi,

I don't think that you can easily do this in BIRT today. Our current
crop of BIRT reports can present Jazz-related data from two locations:
the data warehouse, and the repository.

1. The data warehouse consists of historical data periodically
aggregated from the repository. Our current aggregation story does not
include the links between work items (or more generally between items).
2. The access that we provide to live data from the repository from
within a BIRT report is somewhat limited at the moment. It consists of
only a couple of item types (build results and work items) and does not
allow you to navigate through the links between them.

I think this is a good idea for a report, however, and we should look at
this capability during our planning for the next release. Could you
please open an enhancement request in the Reports component?

Thanks,

james
Jazz Reports Team Lead