New & Noteworthy for Jazz Reporting Service 7.0.1

	Description
Browser Support	Jazz Reporting Service officially supports the Chromium Edge browser Jazz Reporting Service (JRS) now officially supports the Chromium-based Edge browser. Also, the Internet Explorer browser is no longer supported.
User Interface	New style for UI components: Buttons, links, breadcrumbs, modal dialog boxes, and tabs Select user interface components (buttons, links, breadcrumbs, modal dialog boxes, and tabs) are restyled in Jazz Reporting Service (JRS) as part of the ongoing task to align with IBM's open source Carbon Design System. Image of buttons (before and after): Image of links in Data sources page (before and after): Image of breadcrumbs in Data source page (before and after): Image of Remove column dialog box (before and after): Image of Choose report owners dialog box (before and after):
Data Collection Component	Requirement revision history data from DOORS and DOORS Next available in Report Builder Data Collection Component (DCC) now loads the revision history of requirements from the IBM Engineering Requirements Management DOORS® and IBM Engineering Requirements Management DOORS Next applications. You can create reports on requirement revision history. Image of the revision history artifact selected in Report Builder:
Lifecycle Query Engine	Dataset suspension feature is enabled by default Write operations to the Apache Jena TDB dataset occur only when there are no read operations. Write operations are not the same as committed changes. Committed changes are placed into writeback journal files, three journals per TDB. Only when read operations complete, the journal files are flushed to the TDB indexes. Long running or continuous read operations can cause the journal files to grow too large. Large journals increase query times because the read operation looks into both the indexes and journals for the most recent data. This process creates a feedback loop, which can lead to Java™ virtual machine (JVM) heap or stack exhaustion. To address this problem, you can use the dataset suspension feature in Lifecycle Query Engine (LQE). A dataset suspension does the following tasks: Blocks all new read and write operations to the dataset Waits for existing read operations to complete Attempts to flush journal writebacks to the index The following LQE advanced properties control dataset suspension: Heap Suspension Enabled: Initiates dataset suspension when a heap threshold is exceeded. This property is disabled by default. Heap Usage Threshold: Percentage of heap that is used to trigger suspension. The default is 85%. Stack Suspension Enabled: After a commit, initiates dataset suspension if the number of pending journal writes exceeds the maximum pending writebacks threshold. This property is now enabled by default. Maximum Pending Writebacks: The threshold of pending writebacks when stack suspension takes place. Suspend Timeout: The number of seconds to wait for read operations to complete before attempting a journal flush. This value must be greater than the total of query timeout and the rogue query timeout. For example, if the default query timeout is 600 seconds and default rogue timeout is 180 seconds, this value must be greater than 780 seconds.
	New section available in the Data metrics page to add configurations and view added configurations The Available configurations section in the Data metrics page is replaced with the Selected configurations section. You can add configurations and view added configurations in the new Selected configurations section. The earlier user interface took time to render the navigation tree when there were many configurations available for selection. The enhanced user interface with the new section renders faster. Image of the new Selected configurations section:
Report Builder	Append and merge traceability paths in a single report You can now mix Append and Merge traceability paths in a single report. Merge paths take precedence and are evaluated first; then the results are appended together. Image of Append and Merge traceability paths:
	Custom Work Item type attributes are available as links and conditions when you build reports on an LQE data source You can now create reports for the following types of Work Item custom attributes on a Lifecycle Query Engine (LQE) data source: Team area Team area list Project area Project area list Iteration Iteration list These attributes are available when you add conditions and columns.
	Draft reports are cleaned up periodically Draft reports are now deleted based on the value set for the draft.report.max.modified.age.days property in the JTS_install_dir/server/conf/rs/app.properties file. If the number of days since the report was last modified is more than the value in this property, the report is deleted. The default value for the property is 15 days.
	New buttons available to delete tags from multiple reports, schedules, and results In the Group by tag view, you can delete tags from multiple reports, schedules, or results using the following new buttons: Remove tags from reports button on the My reports and All reports pages Remove tags from schedules button on the My schedules and All schedules pages Remove tags from results button on the My results and All results pages Image of the Remove tags from reports button:
	Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.