It's all about the answers!

Ask a question

Modifying existing RTC reports


Kim Soederhamn (1.4k23536) | asked Jul 27 '10, 5:25 a.m.
Hey,

We want to modify the existing "burndown" report into a new report called "critical burndown" the idea is that it should show burndown of workitems but only for workitems with a custom boolean attribute called "critical scope" =true.

We have located and extracted the .rpt report design of the burndown chart and have imported it into the BIRT report designer. unfortunately this report is very complex and is based on a scripted datasource so we dont know how to proceed from here.

Anyone have an idea ?

One answer



permanent link
James Moody (3.3k24) | answered Jul 27 '10, 7:16 p.m.
JAZZ DEVELOPER
Hey,

We want to modify the existing "burndown" report into a new report called "critical burndown" the idea is that it should show burndown of workitems but only for workitems with a custom boolean attribute called "critical scope" =true.

We have located and extracted the .rpt report design of the burndown chart and have imported it into the BIRT report designer. unfortunately this report is very complex and is based on a scripted datasource so we dont know how to proceed from here.

Anyone have an idea ?


Hi Kim,

This is indeed one of our most complex reports, as you have seen. Custom attributes are handled generically to simplify the collection code (i.e. you don't need to tell the snapshots which attributes to collect - they all are). The downside of this is that it's a bit harder to write the reports because the attributes are not surfaced as columns, like you would expect.

In this case, I'd start with the "All Burndown" and "Open Burndown" data sets, which are based on the WORKITEM_STATES table. Change these to work on the WS_BOOL_EXT table (WS = Workitem States, Bool = Boolean type attribute). This looks the same as the workitem_states table with the addition of "KEY" and "VAL" columns. Select both of these as Parameters to the data set. The KEY column is intended as a parameter: pass in the id of the attribute here as a literal. The VAL column will contain the value of that attribute - since you're only interested in ones with a particular value, you can use this as a parameter as well, and pass in true as the parameter value. Make these changes to both All Burndown and Open Burndown.

Now, an additional complication with the Burndown report is that it has *live* data points as well. See pretty much all the data sets starting with "Live". These are based on the LIVE_WORKITEM_CNT table, which fortunately already supports custom attributes. You want to use the BOOLEAN_KEY and BOOLEAN_VAL columns, select them as parameters, and treat them exactly the same as described above.

You shouldn't need any additional *report* parameters, however, and the burndown chart should work as it did before, just with less data because you're filtering. You shouldn't need to modify any of the scripting.

Also note that if you want to run this in the dashboard, you'll need to make similar changes to the micro/Micro Burndown.rptdesign report, and depoy both of them. (The Micro reports are smaller and used in the dashboard, but are otherwise similar in structure to the full-sized reports).

Hope this helps, let me know if you need any further assistance with this.

james
RTC Reports Team Lead

Your answer


Register or to post your answer.