What's new in Jazz Reporting Service 7.1

Edit online

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

Milestone 10

Report Builder
Option to enable or disable the custom BIRT report rendering

Custom BIRT reports can sometimes slowdown the server. You can now use Allow rendering custom reports server property to enable or disable the custom BIRT reports.

The default value of the Allow rendering custom reports server property is True. To disable the rendering of the custom BIRT reports, set the property to False.

Lifecycle Query Engine
Use custom attributes from child artifact types when reporting on top-level artifact types in Lifecycle Query Engine reports
When you are reporting on top-level artifact types such as Work Item or Requirement in Lifecycle Query Engine reports, you can now use custom attributes from child artifact types in the report. Hence, if same custom attribute is added to multiple top-level artifact types and you want to create a report on it, you no more need to create a separate traceability path for each type of artifact that you want to report on.

Milestone 9

Report Builder
Table drill down
You can drill down into the report results in Report Builder by clicking the required entry in a table when an additional level of detail is available. The additional information is available only for the columns that are configured for the same. For example, you can configure a column to process the count of completed, implementing, or backlog work items in a project area.
The image displaying the table cells that are linked with additional information:
To view the additional information in the report results, click the linked content in the table cell, such as the count of completed, implementing, or backlog work items.
Image displaying the completed work items in the Release Engineering project area:
Set the maximum size and age of query history by using new Report Builder server properties
You can now use the following server properties in Report Builder to set the expiry of query history and report caching:
  • Maximum size of query history: The maximum size of query history must be a value between 1000 and 1000000. If maximum age of query history value is nonzero, then the query history maximum size value is ignored.
  • Maximum age of query history in days: The maximum age of query history must be a value between 0 and 365 days.
    Note: If both the maximum size of query history and maximum age of query history in days are set, then maximum age of query history in days takes precedence.
  • Cache report results per user: If true, report results are cached for each individual user. The same report result is not shared by more than one user. Caching the report results per user can improve tracking of report data usage.
For more information, see Report Builder configuration properties.
Report on additional LQE historical metrics

You can now report on more dimensions to the following Lifecycle Query Engine historical metrics in Report Builder.

For Work Item Totals
  • Resolved
  • Resolution
  • Found in
  • Severity
  • Priority
  • Team Area
For Work Item Creation
  • Resolved
  • Resolution
  • Found In
For Work Item Closure
  • Resolved
  • Resolution
  • Team Area
  • Filed Against

Milestone 8

This milestone contains only quality improvements.

Milestone 7

Lifecycle Query Engine
Enable Lifecycle Query Engine Relational store during Jazz Team Server
You can now enable the Lifecycle Query Engine relational store during the Jazz Team Server setup. The Report Builder detects whether LQE relational store is enabled in LQE. If it is enabled, then Report Builder enables the LQE relational store for reports so that the reports can be created by using LQE relational store.

Previously, to enable the LQE Relational store, you had to go to the LQE admin page and enable relational store after the Jazz Team Server setup. To enable the LQE relational store for reports, you had to go to the Data sources page in Report Builder and enable it.

Milestone 6

Report Builder
Improved Data completeness check feature
When you perform the data completeness check for a report in Report Builder, you can now view the message about number of the data sources that are processing the change logs. If the message states that the LQE is processing the change logs, it implies that the data might be incomplete. Wait until the Lifecycle Query Engine completes the change log processing and is up to date. For more information, see Run the report with data completeness check enabled.

Image displaying the data completeness information:

Wild cards for additional operators on string properties
Use Supports wildcards checkbox in Report Builder for query conditions on string properties. By default, the checkbox is set to true when the contains or does not contain operator is selected and false for all the other operators. However, you can change that based on the requirement. Previously, the Report Builder used an unquoted asterisk as a wildcard for the contains and does not contain operators. When the unquoted asterisk was specified for is, is not, starts with, or ends with, the asterisk was always treated literally.

If you select the Supports wildcards checkbox, an unquoted asterisk is taken as wildcard for all the operators. If the Supports wildcards checkbox is not selected, an unquoted asterisk is taken literally. For more information, see Querying on string properties.

View Reports page now displays the Recent configurations
On the View Reports page, when you click the Filter icon, the Recent configurations field is added under the Configurations tab. This field shows the last five configurations that were recently used. By default, the most recent configuration is selected. If a recent configuration is used, you do not need to select the domain, project area, component, and configuration.

To use a different configuration, you can select the Find the configuration option and then select the domain, project area, component, and configuration.

Lifecycle Query Engine
Updated Link Index Provider with the new Lifecycle Query Engine relational store backend
The relational store can now be enabled for the Link Index Provider web application by using the same procedure as the one for the Link Index Provider. For more information, see Installing and enabling LQE relational store. Before you enable the relational store for LDX, consider the following requirements:
  • The LDX relational store must be a different instance than the one for LQE.
  • The database must be created by using the data warehouse setup page of the Jazz Team Server setup wizard.

Milestone 5

Report Builder
Actions when viewing a report
You can now access information about the artifact by clicking the artifact link in the Report Builder. To view the summary of an artifact, hover over the artifact link; a dialog box appears with all the details. For more detailed information about the artifact, click the artifact link to open it in the new tab. For more information, see Viewing reports.

The image displaying the dialog box with artifact details:

Move items by dragging over the breadcrumb node
In Report Builder, you can now move items to any parent folder by using the breadcrumb. Previously, to move or copy one or more items to a parent folder, you had to select the items and then use the Move feature to move them to the intended folder. However, with this new feature, you can simply select and drag the items over the breadcrumb node to move them to the desired parent folder. For more information, see Moving reports or folders.
Optimized the searching feature in Report Builder
The Search all folders button is updated to Search including subfolders in Report Builder. Go to the main reports page in the Report Builder, and select Search including subfolders to apply the scope of the search. With this feature, you can optimize the report search process by setting the scope of your search to include the subfolder, starting from the current folder in the Report Builder. Previously, selecting Search all folders would search all the folders in Report Builder. For more information, see Searching.

Image displaying the Search including subfolders:

The upgrade log indicates whether the rs/db folder and rs/metaModelCache folders were copied or not
When you upgrade the JRS in a side-by-side configuration, the rs/db folder and rs/metaModelCache folders are not copied to the destination folders if the folders exist. Now, the following messages are displayed to show whether the copy command was successful or failed:
SUCCESSFUL
Copied directory from $oldAppPath to $NewAppPath.
WARNING
Did not copy the directory from %oldAppPath to %NewAppPath as it existed.
FAILURE
Failed to copy directory from %oldAppPath to %NewAppPath.

The image displaying the warning messages:

View Reports page displays the artifacts and relationships details
Previously, the capability to view the metadata of the report was not available in the new Report Builder UI. For more information, see Viewing report data and properties.
View Reports page displays the conditions details
Previously, the capability to view the metadata of the report was not available in the new Report Builder user interface. For more information, see Viewing report data and properties.

Milestone 4

Report Builder
Interact with table of report results
In Report Builder, you can now interact with a table of report results that displays data based on selected data types, columns, and artifacts. On this table, you can search, filter, sort, change the size of the display records per page, and resize the column width. This makes it easier to find the data you need and customize your report.

The image displaying the search and filter icon in Report Builder:

Larger report loading indication
You can now see a report loading indicator when you view a report in the Report Builder. This loading indicator displays the loading percentage of the reports whose average loading duration is more than 10 seconds. For more information, see Viewing reports.

Image displaying the report loading indicator in Report Builder:

New actions available when viewing a report
Based on your access permission, you can now edit and copy a report, export the report data, and compare query results between SQL and SPARQL in Report Builder. The compare query option is only available when a customer has both Lifecycle Query Engine Jena and LQE rs. To perform these actions, click the respective icon or option from the page action toolbar. If you are an editor, you can see an Edit button on the page action toolbar by using which you can edit a report. If you are a viewer, you can copy and export a report and compare the query results of the report. For more information, see Working on reports.

Image displaying page action toolbar for the editor:

Image displaying page action toolbar for the viewer:

Lifecycle Query Engine
View the status of validating or indexing selected resources
You can now see the status of the insertion or deletion of the selected resources during indexing, reindexing, and validation in LQE. Previously, the progress of the insertion and deletion of the resources during indexing, reindexing, and validation was not displayed on the LQE admin user interface; it used to run in the background. Having this information on the user interface helps the user to track the progress of their process. For more information, see Monitoring indexing activity statistics.

The image displaying the status of insertion and deletion of selected resources in Report Builder:

Milestone 3

Report Builder
Report data and properties are available on the Report Builder view page
You can now view the report data and properties on the Report Builder view page. Previously in the Report Builder classic, the user had to go to My Choices or edit the report to view the attributes.

To see the report data and properties in the Report Builder, click to open the report. From the Report settings page on the View page, click the Data or Properties tab to see the report data or properties. For more information, see Viewing report data and properties.

Image displaying Data tab:

Image displaying Properties tab:

Disabled naming reports with the same name at the same level
You can no longer use identical names for reports at the same hierarchical level in Report Builder. This change reduces the processing time and efficiency of reports in Report Builder. For more information, see Best practices for creating reports with Report Builder.
Lifecycle Query Engine
Monitor the configuration scope of queries in the Lifecycle Query Engine
You can now monitor the configuration scope of queries in the Lifecycle Query Engine . From the Health Monitoring tab in Lifecycle Query Engine, click Queries to see the query statistics. On the Query Statistics > Completed Queries tab, you can see the Config scope column displaying the version resources count. The administrators can review the Global configurations (GC) count from the Config scope column. If a query has a larger config scope value, then the administrator can suggest to the user, to optimize the query and use a GC with a smaller scope. For more information see, Monitoring indexing activity statistics.
Provide additional Lifecycle Query Engine notification events
In Report Builder, you are now notified of additional events that are related to compaction and data set suspension failures. This helps the administrators monitor the health of the LQE servers and take corrective actions.

To receive the notifications, the administrators can add recipients to the compaction and data set suspension failures by enabling the notifications from https://<server>/lqe/web/admin/notifications.

On compaction failure, an email about the failure is sent to the recipients and the compaction schedule is disabled. They need to rectify the cause of failure and enable the compaction schedule.

On data set suspension failure, an email is sent to the recipients about the failure and the cause for the same. For more information, see Setting up email notification for Lifecycle Query Engine events.

What's new in other Engineering Lifecycle Management applications