What's new in Jazz Reporting Service 7.2

Learn more about what's new and changed in Jazz Reporting Service 7.2.

Milestone 12

Report Builder
Advanced properties to control data warehouse report creation and editing
As a Report Builder administrator, you can now control whether users are allowed to create or edit reports using Data Warehouse (DW) as a data source by using the following advanced properties:
  • enable.report.creation.dw

    This property allows you to enable or disable the report creation using data warehouse. The default value of the enable.report.creation.dw property is True, which means users can create data warehouse reports. When disabled, the data warehouse will not appear as a report type, preventing new data warehouse report creation. Existing data warehouse reports can still be run.

  • enable.report.edit.dw

    This property allows you to enable or restrict editing of existing data warehouse reports. The default value of enable.report.edit.dw property is True, enabling users to edit data warehouse reports. When disabled, the DW reports can be run but not modified.

Improved data provider diagnostics
You can now identify and review data providers that are used during report generation in Report Builder. This enhancement helps you quickly locate and assess the data providers and take corrective action to ensure report accuracy and completeness.
Lifecycle Query Engine
Real-time config cache ID generation for streamlined data export
You can now generate config cache IDs in real time for your selected configurations. This new capability makes it easier to export the latest data from Lifecycle Query Engine and import it into your database or data lake. By automating the data transfer process, you reduce manual effort and improve the accuracy and efficiency of your integration workflow. This feature is available as a JAR or class file on the beta program website.

Milestone 11

Report Builder
Wildcard search support in the configuration picker
You can now search for project areas, components, and configurations using wildcard characters such as * (asterisk) and ? (question mark). This enhancement improves search flexibility by allowing partial or fuzzy inputs, helping you find relevant items more efficiently. Previously, searches required exact matches, which could lead to missed results and additional effort.

For example, to search configurations while creating a configuration-scoped data source in Report Builder.

To use a wildcard search in Report Builder:
  1. Click the Administration icon.
  2. In the left navigation menu on the Administration page, select Data sources.
  3. For the data source where you want to create a type-scoped data source, click the More actions icon, then select Create type scoped data source.
  4. In the configuration picker, enter your search using wildcard characters. If the report uses a configuration-scoped data source, the View report page also supports wildcard search in the configuration picker.
Improved navigation in Report Builder

When you scope a report or query to a configuration, the selection dialog now displays components and configurations as hyperlinks. You can click the hyperlink to go to the related component or configuration. Previously, the components and configurations appeared as plain text.

Validate and export reports while editing

You can now validate and export reports directly while editing in Report Builder. When you open a report, it is automatically validated. If there are issues, an error message appears so you can fix them early. You can also export the report at any point during editing. For more information, see Validating reports and Exporting reports and scheduling reports.

Conflict detection for URI metamodels in Report Builder
You can now identify and resolve conflicts when similar attributes have different types in Report Builder. If a conflict exists, the affected attributes appear with a warning.
To resolve conflicts:
  1. Go to the Type Explorer page.
  2. Select the type that is causing the conflict.
  3. A dialog displays the origin of the conflict. For example, if an attribute is used in multiple project areas, the dialog lists those areas.
  4. Click on the Project area or stream and update the attribute.
  5. After the Report Builder is refreshed, the conflict is resolved.

    Image displaying the dialog with details about the type:

Enhanced traceability for requirement collections

You can now include modules from a requirement collection in your reports by using the uses traceability link. This enhancement introduces a new traceability path for requirement collections and updates how traceability works for individual requirements.

Previously, a requirement collection could only be linked to individual requirements:

  • Requirement collection → uses → Requirement
With this enhancement, you can use the uses traceability link in the following ways as well:
Traceability path Description
Requirement → uses → Requirement Link one requirement to another.
Requirement → uses → Requirement collection Link a requirement to requirement collection.
Requirement collection → uses → Requirement collection Link one requirement collection to another. This automatically includes all modules from the linked collections.
Lifecycle Query Engine
System Alerts in Lifecycle Query Engine or Link Index Provider
You can now view system alerts that are related to maintenance, migrations, and outages in the Lifecycle Query Engine (LQE) or Link Index Provider. To view alert details, click the alert icon that is located above the action menu in the LQE banner. A dialog box opens, displaying system alert information.

Image displaying the alert dialog in Lifecycle Query Engine:

LQE Admin page showing a dialog box displaying alert.

Improved data metrics functionality

You can now search metrics and sort the metric table in Lifecycle Query Engine. The metrics table displays the status of each metric (running or completed) and the duration of the most recent task execution.

These enhancements help you quickly locate specific metrics and monitor their execution status. For more information, see Collecting historical metrics.

Historical metrics new limits and defaults

As a Lifecycle Query Engine administrator, you can now run collection jobs in parallel by configuring the number of collection jobs, streams, metrics, and threads in LQE.

To configure these settings, go to the Lifecycle Query Engine Administration > Advanced Properties > Internal Properties page and update the following properties:

Property Description Default value
app.historyJobs.collectionsLimit Number of collection tasks that can be created. 10
app.historyJobs.collectionStreamLimit Number of streams per collection job 5
app.historyJobs.collectionMetricsLimit Number of metric tasks per collection job 50
app.historyJobs.numThreads Number of threads to use for running history jobs. min(10, max(1, number_of_cpu * 0.75))
For more information, see Lifecycle Query Engine configuration properties
View configuration data volume in Lifecycle Query Engine

As an LQE administrator, you can now view the number of rows in the Selections and Selects tables. These tables contain configuration data, and the added visibility helps you assess the volume of configuration data in LQE. This enhancement improves serviceability by helping you evaluate the size and impact of configuration data more effectively.

To view configuration data volume in Lifecycle Query Engine:

  1. Go to Health Monitoring > Statistics in LQE.
  2. On the Statistics page, scroll to the Selections and Selects table size information section.
  3. Review the row counts for each table.
Jena support removed in Lifecycle Query Engine

Starting with version 7.2, support for Jena in Lifecycle Query Engine (LQE) has been removed. The LQE relational store is now the only supported storage mechanism. This update improves performance and simplifies maintenance by standardizing on a single storage backend.

Note: Before you upgrade to 7.2, you must migrate your SPARQL reports from Jena to relational store. Upgrading disables Jena support entirely.

Milestone 10

This milestone contains only quality improvements.

Milestone 9

This milestone contains only quality improvements.

Milestone 8

This milestone contains only quality improvements.

Milestone 7

Report Builder
Improved bar chart
You can view reports in updated stacked, grouped, or simple bar charts format in Report Builder. If the report has the default graph representation of the dataset in bar chart format, then run the report to view it as bar chart else edit the report to switch to this view and then run the report.

Managing and grouping report conditions
You can edit or add group conditions for a report.
  1. Open the report by selecting a report that you want to edit and click the Edit report icon. The Report settings page opens with the editable fields.
  2. On the Data tab in Report settings page, go to the Conditions section and click Add or edit conditions to add or remove the conditions in your report.
  3. On the Conditions page, click Add group to add group conditions for a report.

Group rows of the report
In Report Builder, when a report is sorted by a specific column, the rows corresponding to that column are grouped, making the report more organized and readable.

To sort the columns of the report to view the grouped rows, complete the following steps:
  1. From the report list, select the report that you want to edit and click Edit report.
  2. Go to the Format result tab.
  3. Set the sort type of the row to ascending or descending.
  4. Run the report.

Customize report export with filters
To apply a filter to the report while exporting:
  1. On the Reports tab, select the reports that you want to export.
  2. Click More actions and then select Export or Schedule.
  3. In the Export or Schedule dialog box, complete the three steps: Format, Filter, and Schedule.
    1. Select the report format and click Next.
    2. Apply filters and click Next to schedule the report export or click Export.
Image displaying the Export or schedule dialog box:


Removed Make the results dynamic button from the Microsoft Excel report
When using Download a spreadsheet with live data export option in Report Builder, the Make the results dynamic in Step 2 and the Refresh Query results button in Step 3 in the report produce same results. Hence, the Make the results dynamic button is now removed from the exported Microsoft Excel report. To refresh the query results, you can now follow the following steps:
  1. If there is a protected view warning in the command bar, click Enable editing. To fix a subsequent security warning about disabled macros, click Enable content.
  2. On the QueryResults sheet, click Refresh Query results to create connection with the data source.
  3. Click Data > Refresh All in any sheet of the workbook to refresh the data.

Integrated system alerts
You can now see system alerts in Report Builder. These alerts display on the Report Builder during maintenance, migrations, and outages. To view alert details, click the information icon next to the Administration icon. A dialog box then displays system alert information.

The image displaying the information icon and the alert:


Milestone 6

Report Builder
Improved pie charts
You can view reports in updated pie chart format in Report Builder. If the report has the default graph representation of the dataset in pie chart format, then run the report to view it as such, else edit the report to switch to the pie chart view and then run the report.
For more information about the exporting reports, see Exporting reports to different formats.
Image displaying a report in pie chart format:

Improved line charts
You can view reports in the updated line chart format in the Report Builder new user experience. If the report has the default graph representation of the dataset in line chart format, then run the report to view it as line chart else edit the report to switch to this view and then run the report.

Set report conditions in Report Builder
You can add conditions in your report in Report Builder. To set the conditions of the report:
  1. Open the report by selecting a report that you want to edit and click the Edit report icon.
  2. From the Data tab in the Report settings page, click Add or edit conditions.
  3. On the Conditions window, add rules and group for the report and click Save.
Image displaying the Conditions window:

Lifecycle Query Engine
Retry setting configuration for fetching TRS documents
You can now configure a retry setting in the Lifecycle Query Engine for reading a TRS document separate from fetching TRS resources.
Image displaying the retry settings for TRS feeds in Lifecycle Query Engine:

Report on additional predefined Lifecycle Query Engine historical metrics
You can now report on additional dimensions when using historical metrics and the LQE rs data source.
For Architecture Elements Totals:
  • Architecture type
  • Component
  • Project area
For Work Item Totals, Work Item Creation, and Work Item Closure:
  • Total story points
For Test case results:
  • Workflow state

Define custom historical metrics when using LQE data source
As a report administrator, you can now export the historical metric bundle of a report and use it to create a custom metric in Lifecycle Query Engine. From the report tab listing in Report Builder, select the report that you want to export, and click Export > Export the report to historical metric bundle for LQE deployment. For more information, see Exporting reports to different formats and Collecting metrics for historical trends reports.

Milestone 4

Report Builder
Customize Db2® driver path in Lifecycle Query Engine or Link Index Provider
You can now customize the Db2 driver path to use your preferred driver version instead of the default version included. In the <extract>/server/conf/lqe/app.properties file, update the DB2_ABSPATH variable to the location of the Db2 driver version that you want to use in Lifecycle Query Engine or Link Index Provider.

Milestone 3

Report Builder
Report data completeness check
Check the completeness of your report in the Report Builder. If the report contains incomplete data due to any reason such as the data provider is validating or reindexing the data, a warning message is displayed with details of conditions that is causing report incompleteness. To enable the data completeness feature in Report Builder, add the flag enable.lqe.data.completeness.check.feature=true in the advanced property file and select Run data completeness check checkbox while running the report.
The image displaying the data completeness status message:

Editing report properties
Edit the properties of your report in Report Builder directly from within the report. Open the report by selecting a report that you want to edit and click the Edit report icon. On the Report settings > Properties tab, edit the following report properties as required. For more information, see Creating, editing, or copying reports.
  • Name
  • Description
  • Tags
  • Folder
  • Cache results
  • Owners
  • Visibility
The image displaying the Report settings page with editable property fields:

Web logout URI advanced property
You can now add a web logout URI in Report Builder, which redirects users during the logout process. To enable this function, add the following advanced property in Report Builder, Lifecycle Query Engine, and Link Index Provider. When you set this property to a valid nonblank URL and log out of the application, the browser logs you out of the application and redirects to the web logout URL.
  • In Report Builder, set theweb.logout.url through the UI or in the app.properties file.
  • In Lifecycle Query Engine, set the web.logout.url in the lqe.properties file.
  • In Link Index Provider, set the web.logout.url in the lqe.properties file
Warning about report results duration
When running a report in the Report Builder, you can now see a warning message if the report takes longer than expected. The warning message informs you of the report's execution duration and data source, indicating whether the data is the latest or retrieved from the cache. You can identify and rectify the issues impacting the report execution speed to improve performance. If the data is retrieved from the cache, rerun the report to get the latest information.
The image displaying the warning message for the report with the latest data:

The image displaying the message for the report with the cached result:

Lifecycle Query Engine
Add custom metrics through Lifecycle Query Engine user interface
As a Lifecycle Query Engine administrator, you can now add custom historical metrics from the UI that can be used in reporting. The existing Data Metrics page is changed to handle both tasks and metrics tabs. To enabling adding metrics in Lifecycle Query Engine, add the following files, such as SQL, SPARQL, and TTL as a compressed file in the Lifecycle Query Engine.
In the Metrics tab, a table with all the updated metric lists is displayed. To add the metric:
  • In the Report Builder, go to the LQE Administration page > Data metrics > Metrics tab.
  • On the Metrics tab, click New metric to add a metric.
  • Go back to the Data metrics page to verify whether the metrics table is updated.

The image displaying the Data metrics page:

Additional notification events added to Lifecycle Query Engine
As a Lifecycle Query Engine registered user, you are now notified for the following additional events in the Lifecycle Query Engine (LQE):
  1. If backup of Lifecycle Query Engine is not scheduled or it did not run in the last 7 days, the following notification is sent to the registered user every 24 hours: The backup has not been scheduled or performed in the last 7 days.
  2. If compaction of Lifecycle Query Engine is not scheduled or it did not run since the last 14 days, the following notification is sent to the registered user every 24 hours: Compaction has not been scheduled or performed in the last 14 days.
  3. If heap memory allocation to the Lifecycle Query Engine server is insufficient, the following notification is sent to the registered user every 24 hours: Inadequate heap memory allocation.
  4. When dataset suspension is triggered because the write back journal size reached the threshold and Lifecycle Query Engine is trying to suspend incoming query to clear the write back journals, the following notification is sent immediately to the registered user: Dataset suspension triggered.
These additional notification events help Lifecycle Query Engine administrator to maintain the Lifecycle Query Engine server health.

Milestone 2

Report Builder
App password login with Microsoft Excel live data export

When running Engineering Lifecycle Management by using Jazz Authorization Server (JAS) and if JAS is configured to generate the application passwords, you can use these application passwords to authenticate in the Microsoft Excel live data export.

To generate an application password:
  1. Go to https://localhost:9643/oidc/endpoint/jazzop/personalTokenManagement, where localhost:9643 is the domain of the authorization server, or sometimes the Engineering Lifecycle Management server.
  2. Generate a new application password.
  3. Provide this new password to the Microsoft Excel login prompt with your username to authenticate.
Session Management in Report Builder

The session management in Report Builder is now improved to resume the session after user inactivity. Previously, when a session expired due to inactivity, an unauthorized user error was produced. To address this issue, a login dialog is now displayed in the Report Builder, allowing you to log in and resume your work seamlessly.

The update applies to the actions on the Create report page in Report Builder, such as creating reports, saving reports, running reports, choosing artifacts.

Warning when report results exceed limit

When running a report in the Report Builder, it displays a warning message if the report table result exceeds the query.results.limit property value, indicating that not all results are displayed. To see the complete result, adjust your report filter or condition to stay in the query limit or ask your administrator to increase the query result limit.

The image displaying the warning message about the query limit:

What's new in other Engineering Lifecycle Management applications