Enabling Experimental Features

Dataplane Reports includes some optional, experimental features.

Be advised that experimental features may be changed or removed without notice in future versions of Dataplane Reports.

Contact our support team with any questions about using one of these features, or to share your feedback.

Exclude Old, Inactive Jira Issues from the Dataplane Index

You can exclude old, inactive Jira issues from the Dataplane Reports index in order to reduce the time it takes to rebuild the Dataplane Reports index, reduce index database table size, and possibly improve the performance of certain reports.

This feature is not an issue archiver. Jira issues excluded from the Dataplane Reports index by this feature are still included in reports. However Dataplane Reports will limit itself to reporting on only the current value of these issues' fields; not on the fields' historical values, since historical values come from the Dataplane Reports index.

Dataplane Reports users are not warned if a report is missing historical data for Jira issues excluded from the Dataplane index. If a report charts historical field values for these issues, the report will run, but no historical data will be shown for these issues. Consider if this might cause confusion for your users.

To have Dataplane Reports only index issues that have been updated on or after a given date, set this JVM property to a date of the format "YYYY-MM-DD":

com.arsenalesystems.dataplane.indexer.excludeUnmodifiedIssuesDate

For example to only include issues in the Dataplane Reports index that were modified on or after July 1, 2020, add the following to your Jira installation /bin/setenv.sh file (for a Linux system):

JVM_SUPPORT_RECOMMENDED_ARGS="-Dcom.arsenalesystems.dataplane.indexer.excludeUnmodifiedIssuesDate=2020-07-01 $JVM_SUPPORT_RECOMMENDED_ARGS"

After adding the JVM property, restart Jira and rebuild the Dataplane index to apply the new feature. For Data Center instances, be sure to add this JVM property on all Jira nodes, and set to the same value on all nodes.

See Atlassian's Jira documentation for directions on setting JVM properties on other systems.

With this feature enabled, any issues excluded from the Dataplane Reports index that are subsequently modified will be automatically indexed and no longer excluded from the app index.

To evaluate the number of issues that would be affected by a specific date setting for this JVM property, run an Issues by Date Report with the following configuration:

Time Period: Custom
Interval: Monthly
Start Date: 1990-01-01
End Date: <empty> (default: This Month)
Search (JQL): updatedDate >= "1990-01-01"
Date Basis: Updated Date

On Jira Data Center, the best option for reducing the amount of data the Dataplane Reports indexer needs to process is to use Jira's built-in issue and project archiving instead of this Dataplane Reports JVM property. Dataplane Reports automatically excludes archived Jira issues and projects from its index.

If your Dataplane users do not chart historical values of issue fields in their reports—or you wish to effectively disable the Dataplane Reports indexer for another reason—set this JVM property to a future date (for example "2100-01-01") to exclude all Jira issues from the Dataplane Reports index.

Disable Specific Types of Reports

This feature lets you block users from creating and using specific types of reports, such as the Issues by Date Report or Time from Status to Status Report.

Upon disabling one or more report types:

users cannot create new reports of those types; in the directory of reports, those report types are hidden in the list of available report types under the New Report button
users cannot view or run saved reports of those types; reports of those types are hidden in the directory of saved and shared reports.
all existing Jira dashboards, Confluence gadgets or shared URL references to reports of those types will display an error indicating that the report has been disabled and is not accessible.

This feature does not delete any saved user reports; it only hides and disables these reports from use.

If a disabled report type is re-enabled, all behavior reverts back to normal for reports of that type, with all previously-created user reports of that type once again visible, and any use of these reports on Jira dashboards and Confluence pages restored.

To block users from creating and using specific types of reports, use the following JVM property:

com.arsenalesystems.dataplane.disabledReportTemplates=<COMMA-SEPARATED_LIST_OF_REPORT_TYPE_IDS>

For example, to disable all reports of type Issues by Date Report and Time from Status to Status Report, add the following to your Jira installation /bin/setenv.sh file (for a Linux system):

JVM_SUPPORT_RECOMMENDED_ARGS="-Dcom.arsenalesystems.dataplane.disabledReportTemplates=reportKey.issuesByDateReport,reportKey.timeFromStatusIndirectToStatus $JVM_SUPPORT_RECOMMENDED_ARGS"

After adding the JVM property, restart Jira. For Data Center instances, be sure to add this JVM property on all Jira nodes, and set to the same value on all nodes.

See Atlassian's Jira documentation for directions on setting JVM properties on other systems.

To find the correct report type identifiers to use with the JVM property, for each type of report, go to Dataplane Reports > New Report and create a new report of that type. The unique identifier for the report type is visible in the URL of the new report’s configuration page. For example reportKey.issuesByDateReport in the following URL:

https://<MY_JIRA>/secure/DataplaneReport!default.jspa?report=reportKey.issuesByDateReport

Page Contents

1 Exclude Old, Inactive Jira Issues from the Dataplane Index
2 Disable Specific Types of Reports