2.15 Release Notes

Owned by David Goldstein
Last updated: Aug 12, 2024
2 min read

2.15.2

Maintenance release.

August 12, 2024

Fixes

  • Fixed issue where clicking the issue count link for the "Other" category of report results displayed error 'JQL function "dataplaneReport" contains an invalid argument' in the Jira Issue Navigator and failed to show the list of Jira issues.
  • Fixed issue in numeric report charts where domain axis categories were incorrectly ordered from lowest to highest value instead of from highest to lowest.
  • Fixed issue where the End Date option for sorting sprints used only the planned end date, ignoring the actual sprint completion date. The sprint completion date is now used if the sprint has been completed; otherwise the planned end date is used.


2.15.1

Maintenance release.

August 5, 2024

Fixes

  • Fixed v2.15.0 issue where user names, project names and issue statuses in report results displayed as undecorated, raw keys/values rather than nicely-linked display names and status lozenges.


2.15.0

Customize version and sprint ordering, time-limited report database queries, and indexer auto-syncing.

July 24, 2024

New Features

  • Customize version and sprint ordering.
  • Time-limited report database queries.
    • All report database queries are now limited in duration to 60 seconds, and automatically canceled at the database level if they exceed this time limit. This gives administrators more control of overly-complex, long-running report queries which could cause system performance issues.
  • Automatic Sync Index operations synchronize Dataplane Reports with Jira application changes.
    • To reduce the need for administrators to manually run Sync Index after certain Jira application changes, Dataplane Reports automatically runs Sync Index when Jira custom fields are created or deleted, and runs additional scheduled Sync Index operations several times a day.

Fixes

  • Fixed issue where canceling a Sync Index operation on the app Administration → Configuration page could corrupt the index status, requiring a full index rebuild.
  • To avoid duplicate requests, indexer buttons on the app Administration → Configuration page prevent multiple clicks for the same requested operation.

Page Contents