In the previous article How to Create a Reporting Site

In this article series by John Ward,author of BIRT 2.6 Data Analysis and Reporting we will be looking at :

• Bug Status- A Report to show open issues compared to all bugs
• Developer issues reports-this report will accomplish two things—shows us a Pie Chart showing fixed versus non-fixed bugs and gives us a list of bugs in an open status assigned to that developer.

Bug status

The next report we are going to undertake is the report to show open issues compared to all bugs. What we are trying to build here is a graph that shows, by category, the bugs that are open in relation to the total number of bugs for that category. No other grouping is required. Under the graph, we also want to show a list of open bugs that we can click on and have them drill down to the detail for that bug so that we can see the history of changes to that bug.

What this means is we need a bar graph showing all the status.

1. Open BugzillaReportsTemplate.rptTemplate and save as bugStatusReport.rptDesign.
2. Drag getAllBugs over to the Report Designer.
   
   
3. Delete all columns except the bug_status field and short_desc field.
   
   
4. In the table, group data by the components' name.
   
   
5. With the new category created in the Table, insert a new column on the right. Delete the header labels. Move the data fields to look like the following screenshot:
   
   
6. In the Outline tab, select the root element. Apply bugZillaTheme.
7. In the group header row with the name, apply the DetailTableHeader style.
   
   
8. In the Detail row, apply the DetailTableRow style.
9. In the header row, select all the cells and merge them.
   
   
10. In to the new merged cell, insert a chart.
    

    

11. Select a Bar Chart and change the Output Format to PNG.
    

    

12. Open the Select Data tab.
13. Set the Inherit Data from Container drop-down list to Inherit Columns Only.
14. Drag the bug_status field to the Optional Y Series Grouping slot.
15. Drag the name field to the Category (X) Series slot.
    

    

16. Click on the Edit group and sorting button.
17. In the Group and sorting dialog, check the Enabled checkbox.
18. Set the Type to Text.
19. Set the Interval to 0.
20. Set the Aggregate Expression to Count.
    

    

21. As the Value (Y) Series, enter 1.
    
    
22. Under the Format Chart tab, go to Title. Enter the title as Bug Status Report.
    

    

23. Select the Axis option.
24. Under X-Axis, check the Stagger checkbox.
    
    
25. Click Finish.
26. Resize the chart to fit the number of categories.
    
    
27. The last thing we need to do is add the drill-through from the descriptions to the bug detail. Select the short_desc data item in the report designer.
    

    

28. Under the Property Editor, select the Hyperlink tab.
    
    
29. Click on the Edit... button next to Link To.
30. From the Hyperlink dialog, select the Drill-through as Hyperlink type.
31. Select BugzillaDetailReport.rptDesign as the target report.
    

    

32. Set up the target report parameter bugID to be linked to row["bug_id"].
    

    

33. Click OK and save the report
    .
    
    

BIRT 2.6 Data Analysis and Reporting

Create, Design, Format, and Deploy Reports with the world's most popular Eclipse-based Business Intelligence and Reporting Tool

Published: July 2010
eBook Price: ₨831.00
Book Price: ₨1,386.00
See more

close

Select your format and quantity:

Book 01234567891011121314151617181920

eBook 01234567891011121314151617181920

Developer issues reports

The next report is a combination of the last two reports in our list. Given a developer ID, this report will accomplish two things—shows us a Pie Chart showing fixed versus non-fixed bugs and gives us a list of bugs in an open status assigned to that developer. Let's now build the report:

1. Open BugzillaReportsTemplate.rptTemplate and save as DeveloperPerformanceReport.rptDesign.
2. Modify the getAllBugs query to look like the following:
   

   SELECT
   		bugs.bug_id,
           bugs.bug_severity,
           bugs.bug_status,
           bugs.short_desc,
           profiles.userid,
           profiles.login_name,
           profiles.realname,
           components.id,
           components.name,
           components.description
   FROM
           bugs,
           profiles,
           components
   WHERE 
           bugs.component_id    = components.id 
           AND bugs.assigned_to = profiles.userid
           and profiles.userid = ?

3. Bind the dataset parameter to a report parameter called developerID.
4. We want to use a drop-down list for the developer ID parameter. Create a new dataset to display the unique developer IDs using the following query and call it developerIDList:
   

   SELECT distinct
   		profiles.userid,
           profiles.realname
   FROM
           profiles

   

5. Open the report parameter developerID for editing.
6. Change the Display type to Combo Box.
   
   
7. For the Selection list values option, change the radio buttons to Dynamic. Under the list of datasets, select developerIDList.
   

   

8. For the value column, select userid.
9. As the display text, use the following expression:
   

   dataSetRow["userid"] + " - " + dataSetRow["realname"]

10. As the Default value, enter 1. The dialog should look like the following:
    

    

11. Click on OK to save our changes.
12. Drag getAllBugs dataset over to the Report Designer.
13. Delete all columns except bug_id and short_desc.
    
    
14. Insert a new row in the header above the column labels.
    

    

15. Merge all the cells in the new row.
16. Insert a chart into the new large cell.
17. Select a Pie Chart and set the Output Format to PNG.
    

    

18. Select the Select Data tab.
19. Set the Inherit Data from Container drop down item to Inherit Columns only.
20. Under the Category Definition, use the following expression:
    

    if (row["bug_status"].toUpperCase() == "RESOLVED")
    	"Fixed";
    else
    	"Open";

21. Click on the Edit Group and Sorting button.
22. Check the Enabled option under Grouping tab.
23. Set the Type to Text.
24. Set the Interval to 0.
25. Set the Aggregate Expression to Count.
    

    

26. Click OK.
27. Under the Slice Size Definition, enter 1 for the value.
    

    

28. Under the Format Chart tab, go to Title.
    
    
29. Change the Title to Open Issue Chart.
30. CLick Finish
31. Resize the chart.
32. Change the labels for Bug ID and Bug Short Description.
    

    

33. Select the Detail row of the chart.
    
    
34. Under the Property Editor, select the Visibility tab.
35. Check Hide Element.
36. Use the expression, illustrated in the following screenshot:
    
    
37. Select the bug_id data element.
38. Under the Property Editor, select the Hyperlink tab.
39. Click the Edit... button.
40. Create a drill-through to the detail report using the column binding's bug_id as the parameter value.
    

    

41. Select the root of the report in the Outline tab, and apply bugzillaTheme.
42. Apply TableHeaderStyle to the header row.
    
    
43. As we used the visibility expression to hide rows that are resolved, this will throw the Highlight used in the DetailRow style off. So, we are going to use a little bit of scripting to apply our highlight. Open up the Outline view.
44. In the Report Designer, open the Script tab.
45. Select the Reports Root element and, in the Script editor, choose the initialize method.
46. Type the code shown in the following screenshot in to the Script editor:
    

    

47. Select the Detail row in the Outline tab.
    

    

48. In the onRender method, type the following code:

    if (this.getRowData().getColumnValue("bug_status").toUpperCase() == "RESOLVED")
    {
        displayedRow++;
    }

    
49. In the Property Editor, select the Highlight tab.
50. Create a Highlight using the following code:

    displayedRow % 2 instead of row.__rownum

    

51. Save and preview the report.

The reason this worked is because we needed to get the values in the data rows before the visibility rule takes effect. Once we have those components created, we check in the Render phase to see if the value of bug_status is set to the RESOLVED value. If not, then we advance the counter that would normally be advanced by ROWNUM. This keeps it nice and uniform.

Summary

In this article we looked at a realistic example of a series of reports that could be used in a real life project.

We have illustrated just about every major element of reporting with BIRT, from Report Projects, Report Components, Charts, Scripting, and Formatting. We even looked at how to look at requirements and find reports with similar specs and data, and how to combine reports. If a single report can take the place of multiple reports and tell a more complete story, it is always beneficial to do so. In addition, we also introduced the Visibility rule, which is very similar to the Highlight rule. These reports can now be deployed to a report platform and be used for production reports.

BIRT 2.6 Data Analysis and Reporting

Create, Design, Format, and Deploy Reports with the world's most popular Eclipse-based Business Intelligence and Reporting Tool

Published: July 2010
eBook Price: ₨831.00
Book Price: ₨1,386.00
See more

close

Select your format and quantity:

Book 01234567891011121314151617181920

eBook 01234567891011121314151617181920

About the Author :

Books From Packt