Reporting on artifacts across projects with Report Builder
Using Report Builder, you can create reports to view data from across your projects.
For example, create a report to determine whether you have adequate test coverage and to ensure that defects are identified and tracked. 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. In this case, you create a report about requirements, related test cases, and the defects that are related to those test cases.- To learn about reporting on data in configurations, see Reporting on data in configurations in IBM® Knowledge Center and Getting started with reporting by using Lifecycle Query Engine data sources on Jazz.net.
- To create historical metrics reports about artifact and project trends, see this topic.
About this task
Procedure
Step 1. Choose data
Procedure
Step 2. Format results
Procedure
- Format the results to determine whether to show the report as a table or a graph.
- Click Refresh to see a sample layout of your report. To see all the data, you must run the report.
Step 2a. Show the report as a table
Your report already has some columns, including columns for the attributes you created conditions for.
Procedure
Step 2b. Show the report as a graph
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.
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.
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
You can use the dynamic Filters option to edit the configuration or conditions set for the report. When you clear dynamic filters, the default choices from the report, which include the conditions specified in the "Set conditions" section and the projects selected in the "Limit the scope" section, are retained.
If you show the report as a table, you can add and change filters on columns by clicking the pencil icon.
- To change the filter values, click that icon.
- To see which filter values are applied, hover over the column name.
If you choose an LQE-based data source in Step 1. Choose data 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.
For more information, watch the following video:
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 various document types (Microsoft Word, PDF, HTML). To do further editing on the report, export it to IBM Engineering Lifecycle Optimization - Publishing if you have a license. You can also export a report graph to an image file. See the related topics.