2.3 Release Notes

Improvements

• Jira 7.11.2 compatibility

Improvements

• Jira 7.10 & 7.11 compatibility

Improvements

• compatibility with Jira 7.5
• for SQL Server, significant speed improvements to reports using a custom field for "Date Basis"
• for Oracle and PostgreSQL, major speed improvements when running Issue Values Snapshots (Sum) by Date reports
• improvements to the responsiveness of the "Search" control on systems with a large number of agile boards
• reduced all report runtimes by a few seconds across the board for systems with a large number (500k+) of issues
• Jira can now be stopped and restarted during the Dataplane nightly history index extension task without corrupting the Dataplane index. This enhances reliability for all systems (but particularly for Data Center instances)

Fixes

• corrected problems (introduced in 2.3.5) with excess logging to the Jira log when duplicate values were found in the Dataplane index

Requirements Changes

• the minimum supported version is now Jira 7.0
• SQL Server 2005 is no longer supported (consistent with Jira 7.0 platform requirements)

Improvements

• Browser Improvements

  • Javascript optimizations to improve responsiveness of the Reports Directory with large numbers of saved reports.

  • Javascript optimizations, for Windows Edge and IE10 browser clients, to eliminate delays in closing dialog boxes in the Reports Directory.

• Indexer Improvements
  • Improved speed of Dataplane indexer task that runs at the end of every month.

Fixes

• JIRA Data Center Fixes

  • For JIRA Data Center instances, added graceful recovery for a situation where one of the Dataplane indexer tasks might permanently terminate under certain conditions.
• Memory Usage Fixes
  • Fixed a memory leak that occurred on JIRA 7.1+ while generating a list of issues for the report.
  • Reduced memory usage and Java garbage collection thrashing during the Dataplane indexing proces.
  • Fixed excess memory usage when running Dataplane reports on JIRA dashboards and navigating away from the page.
• Database Fixes
  • Fixed condition where unexpected database server shutdown or database connectivity issues could cause Dataplane to leak database pool connections.
  • Fixed MySQL issue where, under certain conditions, report generation would fail with the message "The table QTTxx is full".
  • Fixed Oracle issue where certain reports would fail with an ORA-01795 error if a JIRA instance had more than 1,000 statuses.
• Add-on Conflict Fixes
  • Fixed a conflict between Dataplane and various other add-ons, including Tempo Timesheets and Xray Test Management. When these add-ons were run together, various Dataplane drop-down lists would malfunction.
• Other Fixes
  • Fixed bug where report subscription emails received via Microsoft Exchange would end up with the generic filename "attachment", without any .pdf suffix, and could not be opened in a PDF viewer application without renaming.
  • Fix for JIRA 6.1 with Internet Explorer 11 clients. Data series in the chart legend of JIRA dashboard reports were missing their identifying color icons.

Requirements Changes

• Since Dataplane 2.3.1, Dataplane now requires the Java 7 or 8 JRE/JDK. Java 6 is no longer supported.

Improvements

• Added support for JIRA 7.2 and 7.3.

Requirements Changes

• Since Dataplane 2.3.1, Dataplane now requires the Java 7 or 8 JRE/JDK. Java 6 is no longer supported.

Improvements

• Added JIRA 7.1 compatibility

Security Updates

• Corrected a critical-rated remote code execution vulnerability. To successfully exploit the issue, the user must have been authenticated against JIRA and granted access to both Dataplane and Dataplane Customizer Scripts. We recommend that all customers update to this release. Please contact Arsenale Support with any questions, or see the Dataplane Security Notice 2016-03-09 for full details.

Fixes

• Fixed an issue preventing drill-through to the Issue Navigator from Dataplane dashboard gadgets under certain conditions. After a dashboard was first loaded, right-clicking on a drill-through link would fail with the following error displayed in the Issue Navigator: "JQL function 'dataplaneReport' refers to report details that are no longer available". Users are now required to left-click drill-through links in order to access report details in the Issue Navigator. Drill-through links are no longer accessible via right-clicking.

• Fixed two problems in JIRA 6.x instances for users whose username (login) had been renamed:

  • Drill-through from report results to the JIRA Issue Navigator would fail and display a permission error when invoked by these users.

  • The list of Recent Reports in the Dataplane Reports JIRA menu would remain empty for these users.

• The PDF export of entire JIRA dashboards sometimes omitted the titles of certain reports. This occurred most often when a gadget was configured to show a table of results only, and that report had no report descriptions enabled.

• Removed excessive space between plotted series bars when a grouped bar or grouped column chart is selected for Chart Type.

Requirements Changes

• Since Dataplane 2.3.1, Dataplane now requires the Java 7 or 8 JRE/JDK. Java 6 is no longer supported.

Improvements

• Added JIRA 7.0.2+ compatibility

Fixes

• The Epic Name, Epic Link and Epic Status fields now show the same data as the equivalent fields in the standard JIRA Issue Navigator. This is a breaking change which requires any report that uses the Epic Name field to be reconfigured. Previously, the "Epic Name" field incorrectly returned the equivalent of the "Epic Link" data (the name of the epic to which the issue was linked). This field now correctly returns the name of an epic when applied to the epic parent issue. Reports that applied the Epic Name field to child issues in an epic should instead be revised to use the Epic Link field instead, which will produce the desired name of the linked epic. To get a list of saved reports that are referencing the “Epic Name” field:

  • find the custom field ID for “Epic Name” in your JIRA instance.  Go to the JIRA Administration -> Issue -> Custom Fields, find the “Epic Name” entry and click on the toolgear->“View” link. Write down the customFieldId for that field in your instance from the destination page URL.

  • run the following query on your JIRA db, replacing “12601” with the actual custom field ID for “Epic Name” in your own instance:
    

    select "NAME","OWNER" from "AO_6714C7_SAVED_REPORT_RECORD" where ("OPTIONS" LIKE '%12601%');

    You’ll see something like the following if there are saved reports using “Epic Name”:

                                 NAME                             | OWNER 
    --------------------------------------------------------------+-------
     Project Denali - Epics Retrospective (2014+) [by Issue Type] | alex
     Project Denali - Epics Retrospective (2014+)                 | amanda

• Fix for a compatibility issue with JIRA 7.0.2+ that prevented the main Dataplane Reports menu from appearing.
• Fix for an incorrect rendering of Dataplane gadgets while using Wallboard Mode with JIRA 7.0+.
• Fix to restore the functionality of JQL auto-completion in the Dataplane "JQL" tab in JIRA 7.0.+
• Fixed recurring NullPointerExceptions in the log if a user created a subscription to a report, and then that user was later deleted from JIRA.

Requirements Changes

• Since Dataplane 2.3.1, Dataplane now requires the Java 7 or 8 JRE/JDK. Java 6 is no longer supported.

Improvements

• Added support for JIRA 7.0

Fixes

• Fixed a problem for Oracle databases where users could not see the report directory if they had access to 1,000 projects or more, if the user was a member of 1,000 groups or more, or if the user had access to 1,000 saved reports or more.

Requirements Changes

• Dataplane now requires the Java 7 or 8 JRE/JDK. Java 6 is no longer supported.

New Features

• Export JIRA Dashboards to PDF
  
  • Provide a complete picture of your project or program status by exporting an entire JIRA dashboard of Dataplane reports to a single PDF file for sharing with management or your team.
• Customize the Order and Name of Chart Categories
  • Use the new category and categoryRegex keywords in Customizer Scripts to set the sort order and name of domain axis categories in Current Issue Values, Sum Numeric Field and other non-historical reports.
• New Charting Options for the Issues Entering Status by Date Report
  • You can now plot either cumulative or non-cumulative results in the powerful Issues Entering Status by Date report. 
  • A range of new chart types are also available in this report, including column chart, grouped column chart and area chart.
• Advanced Customizer Script Editor
  
  • A graduate of Dataplane Labs, the advanced Customizer Script editor is now a standard feature in Dataplane, making scripting reports faster and more intuitive than ever. Compose clear, syntax-checked report customizations with code editor-like features including auto-indentation, syntax color highlighting and parentheses matching. 
• Easily Hide Empty Results Data

  • To focus on the most meaningful results, click on the new "Include only non-zero values" option in your report configuration to filter out zero-valued entries from the results data table and from exported reports.

• Quickly Revert Changes
  
  • When editing a report, quickly revert unsaved changes back to the last saved version with the new Discard Changes option in the Save menu.
• Dataplane Speaks 日本語
  • Dataplane is now available in Japanese. We would like to extend a large "thank you" to the Atlassian Experts at Ricksoft for doing an incredible job on this translation. (リックソフトが翻訳！ Dataplaneが日本語で使用できます！)

Improvements

• JIRA Agile Compatibility
  • Support for JIRA Agile 6.7+
    
• New and Updated JIRA Fields Support
  • Added support for segmenting results data by JIRA's Status Category property.
  • Added support in JIRA 6.2+ for presenting issue status values in JIRA's new colorized, graphic form.
• Optimized Customizer Script Performance
  • Improved the caching of Groovy scripts used by Dataplane Customizer Scripts. Reports with Customizer Scripts now run significantly faster.
• Improved Robustness of Report Subscription Delivery
  • Report subscription emails now use JIRA's standard outgoing mail queue to allow for deferred delivery rather than canceling sending when the SMTP mail server is momentarily unavailable. 
  • If any errors occur while generating a report for a report subscription, no report is sent and the schedule owner is instead notified by email of the error.
• Localization of Report Subscription Emails
  • Report subscription emails are now sent in each individual recipient's language for all languages supported by Dataplane.
• Expanded Reports Directory Search
  • When selecting a new report, the Search box in the Reports directory now matches on text in the report description as well as the report name.
• Improved PDF Export Layout
  • Improved the handling of page breaks in PDF exports to present report results more concisely.
• Support for Microsoft Edge browser
  • Dataplane now supports the Microsoft Edge (Windows 10) browser with JIRA 6.4+

Fixes

• Eliminated the extraneous series named "None" that, under certain conditions, would appear in the chart legend for historical reports.

• Fixed issue when displaying a JIRA dashboard that contained multiple Dataplane reports. This affected MySQL database-based JIRA instances only. If the dashboard contained Issue Values Snapshots by Date or Issue Value Snapshots Sum by Date reports, the result values displayed in those gadgets could be double or triple the actual values.
  

• Fixed calculation of the minimum, maximum and average statistics for the new grouped chart types in the case where chart data was segmented. This affected reports using the grouped bar chart, vertical grouped bar chart or grouped column chart. Statistics were being calculated as if the charts were displaying non-grouped (stacked) results.

• Fixed divide-by-zero error when plotting vertical bar charts with no categories

• Fixed an issue that prevented users with renamed usernames from being able to subscribe to reports.
• Fixed a dashboard gadgets problem where some multiple-pie charts were clipped at the bottom of the chart with not all individual pies displaying.
• Corrected the aspect ratio in the PDF export of horizontal bar charts.
• Fixes for excess gadget redrawing when vertically scrolling through Dataplane dashboard gadgets on an iOS device.
• ScriptRunner fields now retain their underlying data type when used in Issue Table reports.
• When clicking on a link to a Dataplane page and prompted to first log in to JIRA, after successful login you are now properly redirected to the requested page.
• Temporary PDF files generated by report subscriptions are now automatically deleted from the server after the subscription emails have been sent instead of lingering.
• Fixed the PDF export of Current Issue Values, Sum Numeric Field and similar non-historical reports so extra tall charts are no longer rendered with an unusually narrow width. 
• Fixed issue on JIRA 6.4 when leaving the Reports directory page with a non-empty Search input box; browser no longer prompts for confirmation before leaving the page.

• When viewing saved reports in the Reports directory, the Search input box is now cleared when switching saved report categories in the left-hand sidebar.

• Corrected a compatibility issue with JIRA Data Center for JIRA 6.4.3+

Upgrading From 2.1 or Earlier

If upgrading to this version from Dataplane 2.1.x or earlier, the following apply:

• Upon upgrading to this version, Dataplane will automatically start a full Dataplane reindex. A full Dataplane reindex does not affect JIRA access or performance, but it can take hours to complete on very large JIRA instances. Dataplane reports are unavailable during reindexing, so please schedule your upgrade accordingly.

• Upon upgrading to this version, you will not be able to revert to a prior version of Dataplane. This upgrade migrates the storage of Dataplane reports to a new format which uses unique numeric IDs for JIRA projects and filters instead of names.

• Upon upgrading to this version, if any of your saved Dataplane reports refer to a saved JIRA filter that shares a duplicate name with other filters in your instance and if those reports are shared with other users, this version of Dataplane may end up selecting a different filter than was selected by Dataplane 2.1 or prior. Please contact Arsenale Support if you have any concerns or questions about this issue in your upgrade.

• Before upgrading from Dataplane 1.8 or lower to this release, you must apply the steps in this FAQ.