Reporting on metrics and historical trends across projects with Report Builder
By using Report Builder, you can create reports to identify trends in project or team progress and quality throughout a release, a sprint, or a specific time range.
Report on a single trend or several historical trends in your data. You can define conditions to focus only on the data you need. You can specify whether conditions can be changed when the report is run, so other organizations can reuse and tailor your report.- For detailed information about creating historical trend reports, see this article on Jazz.net.
- To report on current data in and across projects, see this related topic.
- To learn about reporting on data in configurations, see this topic and this article on Jazz.net.
Before you begin
About this task
Procedure
What to do next
- To see your report in the list of other reports, click All Reports or My Reports.
- To further edit your report, click a pencil in the My Choices pane at the right. Click Save to save your changes.
- You can export your report to a spreadsheet or to IBM® Engineering Lifecycle Optimization - Publishing (PUB) as a document-style report. You can also export a report graph to an image file. See the related topics.
Step 1. Choose data
Procedure
Step 2. Format results
The trend report is formatted as a graph by default. Report Builder picks the graph type based on your selections so far. Experiment to find the best graph type. Typically, line graphs convey trend information effectively, but you might find that a bar chart (stacked or grouped) works better with your data.
Procedure
Before you can preview a graph, you must select a value for the unit of measure. You can also select the dimension.
Click Refresh to see a sample layout of your report. To see all the data, you must run the report.
Step 3. Optimize the report
About this task
When you create a report, Report Builder generates the underlying query resource. If you are using Data Warehouse as the data source, an SQL query is generated. If you are using Lifecycle Query Engine, a SPARQL query is generated.
If you want to manually edit the generated query, see this topic. You can also generate alternate queries and optimize your reports based on your requirements.Procedure
Generate alternate queries using the following options. To find what works best, try turning these options on and off. The options appear only when you select Lifecycle Query Engine or Lifecycle Query Engine scoped by a configuration as the data source.
- Select the Defer finding relationships with an alternative query checkbox to generate an alternate query that filters on source artifacts before finding relationships. Try this option if your data has one-to-many relationships in the Artifacts relationships section.
- Select the Defer scoping by projects with an alternative query checkbox to generate an alternate query that filters on artifacts first before scoping by projects. Try this option if your data has large number of projects in the 'Limit the scope section.
Step 4. Name and share the report
Procedure
Step 5. Run the report
To see the complete report, click Run report. Provide values for all required parameters or filters.
About this task
If you choose an LQE-based data source in step 2 and Report Builder reports don’t show the artifacts that you expect, show artifacts more than once, or show a different number of artifacts than application views, ask an application administrator to validate the TRS feeds for the application. See Validating TRS feeds and the LQE index.