...
Can Dataplane report on issues created before it was installed or only on those issues created or modified after installation?
Arsenale Dataplane reports on the entire history of your Jira instance, providing a comprehensive analysis of even those issues created or modified before Dataplane Reports was installed.
When Dataplane Reports is first installed, it automatically indexes your entire Jira instance history including every issue creation, workflow transition, and field value change ever made. Once the initial index is complete, all subsequent changes in your Jira instance are tracked by Dataplane Reports in realtime.
So with Dataplane you get the same detailed insight into past project and team performance and metrics as you have going forward.
How current is the data I'm viewing in Dataplane
...
Reports?
After Arsenale Dataplane Reports does an initial index, upon installation, of your Jira instance history, all subsequent changes in your Jira instance are then tracked by Dataplane Reports in realtime.
So all Arsenale Dataplane reports reflect the most current state of your Jira issues. There is no delay between Jira issue changes and those changes being reflected in Dataplane reportsReports, whether those reports are viewed within Dataplane, on Jira dashboards, or in Confluence via a Dataplane Reports gadget.
Does Dataplane Reports modify Jira project or issue data?
No. All Jira project and issue data is treated as read-only by Arsenale Dataplane Reports.
For its performance-optimized reporting and storing of saved reports and other app user data and settings, Dataplane Reports creates and maintains its own separate database tables within the Jira database.
Is Dataplane Reports subject to the same 1000 issue export limit as the Jira Issue Navigator?
No. Dataplane Reports works completely independent of the Jira Issue Navigator and is not subject to this limitation.
If you have not yet run into this limitation in the Jira Issue Navigator, it refers to trying to do an Excel export of the results of a Jira search and being limited to a maximum of 1000 issues (rows) that can be exported at any one time. This can make it difficult to pull comprehensive Jira data into Excel for additional analysis. The limit built into the Jira Issue Navigator is due to potential performance and memory issues with larger exports. You may increase this limit via a Jira configuration parameter but should carefully monitor instance performance and memory usage in making any changes. Any changes made to Jira's export limit is independent of Arsenale Dataplane Reports and has no effect on your export of issues from Dataplane.
With Dataplane Reports you can easily run reports on and export results containing tens of thousands of issues. Dataplane Reports's Issues Table Report is an excellent substitute for viewing and exporting issues from the Jira Issue Navigator.
Dataplane's report queries are run directly against the Jira database rather than Jira's internal issue cache. So that Dataplane Reports' s database queries are not completely unbounded in result size, Dataplane places a soft limit on database query results of 20 million result items (20,000,000 rows x columns of data). While we expect this limit should be more than sufficient for the majority of Jira instances, if running a Dataplane report produces an error indicating this limit has been reached, you may tune the limit with the following JVM parameter:
...
| Anchor | ||||
|---|---|---|---|---|
|
When using Dataplane Reports gadgets in Confluence, why am I getting an authentication prompt?
On some systems, after you add a Dataplane report to a Confluence page, users see a message similar to the following at the top of the gadget in Confluence:
...
The subsequent OAuth Tokens page will show a list of all of the approved OAuth Access Tokens for the specified user. If you see a large number of tokens that were all approved at around the same time, you may need to go back and double-check the URL configurations.
When using Dataplane Reports gadgets in Confluence, why am I getting a PermissionException error?
When viewing a Dataplane Reports gadget in Confluence, users may get a message such as the following, even though they are correctly logged into both Confluence and Jira:
...
If only one of your applications falls into the above version range, that application still must be patched, since the Application Links in later versions of Confluence and Jira are not compatible with earlier versions in the above range that do not have the patch.
| Anchor | ||||
|---|---|---|---|---|
|
When using Dataplane Reports gadgets in Confluence, why am I getting HTTP 504 timeout errors?
This is caused by Confluence's short default timeout when making HTTP requests to Jira from a Confluence macro. The default timeout in Confluence 6+ is only 5 seconds, and in Confluence 5.x and below it is 15 seconds.
...
Timeout parameter values are in milliseconds, so the above change sets the HTTP timeout to 60 seconds (60,000 ms). If your longest-running Dataplane reports require more time, adjust this value accordingly.
When using Dataplane Reports gadgets in Confluence, why is the gadget blank or cannot be configured?
We are aware of two possibilities:
...
To fix this, adjust Confluence's default HTTP timeout as described above in When using Dataplane gadgets in Confluence, why am I getting HTTP 504 timeout errors?.
| Anchor | ||||
|---|---|---|---|---|
|
Gzip Compression Causes Issues and Blank Gadgets with Jira 5.1 to 6.2.4
...
If you use Jira behind a web server proxy, you may still be able to leave gzip compression enabled on the proxy.
I'm still having problems with rendering Dataplane Reports gadgets in Confluence. Help!
Some customers have reported issues with the Application Links configuration when one application is configured to connect over regular HTTP, but the other application is configured to connect over HTTPS, and that this problem is not specific to Dataplane. Ensuring that both Confluence and Jira use the same protocol may make it easier to set up a working application link.
Jira Issue Fields
What Jira issue fields are supported by
...
Dataplane Reports?
Dataplane reports on a wide variety of Jira field types including:
...
The most common reason for this is, after adding a new custom field to Jira that is supported by Arsenale Dataplane Reports, you must:
- click the "Sync Index" button on the Dataplane Administration page to inform Dataplane about the new field, and
- rebuild your Jira index so that the custom field is useable by Jira
...
- 21.25 hours in an Issues Work Log Table Report is exactly 21.25 hours of actual work completed, regardless of time of day, weekend or holiday
- in a Closure Time Report or Time from Status to Status Report, a display of 36 hours for the average transition time in a reporting interval means 36 hours on a regular 24 hour clock, or 1.5 calendar days, rather than 4.5 working days of 8 hours each.
Fonts
Why are Dataplane Reports charts displaying unreadable font characters for axis labels and values?
Under some circumstances, after installing a new Jira instance or upgrading an existing Jira instance, the font characters displayed on Dataplane chart axes and labels are unreadable.
Dataplane Reports assumes there is a font named "Dialog" installed and available to Java, or "LucidaSans" if on a MacOS server. These are default fonts that come with Java. The Java runtime may be unable to locate this font, or a mangled alternate version is overriding the default installed with Java. If you search your Jira server log file (logs/catalina.out) there may even be a mention of not finding this font.
...
In order to provide high performance historical reporting, Arsenale Dataplane Reports builds and maintains its own optimized index of every change made to the issues in your Jira instance. Once Dataplane's index is built—after initial installation, on upgrade or after manually clicking the Build Index button in Dataplane Administration—all subsequent issue changes in your Jira instance are tracked by Dataplane in realtime.
...
Sync Index tells Dataplane to re-synchronize its realtime indexing with the current state of your Jira instance, picking up any new custom fields or unconventionally created Jira issues. This incremental synchronization is very fast and should complete in under a minute on most instances.
| Anchor | ||||
|---|---|---|---|---|
|
Arsenale Dataplane Reports includes a number of links in the application to allow users to easily open a support ticket with Arsenale: to suggest new features or product improvements, to request help with a feature or report, or to file a bug.
...
If you wish to disable this feature, hiding all product feedback links in Arsenale Dataplane Reports:
Scroll down until you find the listing for Arsenale Dataplane Reports, and click on it to expand the add-on listing.
Click on the link labeled "xx of yy modules enabled" on the right-hand side of the listing. Then scroll down to see the list of individual components ("modules") of the Dataplane add-on.
Find the "Issue Collector Web Resources (issueCollectorWebResources)" module and click on the Disable button that appears when you hover your cursor over that module listing.
...
The feedback module is now disabled, and Arsenale Dataplane Reports product feedback links are no longer visible to users.
| Anchor | ||||
|---|---|---|---|---|
|
No. Uninstalling Dataplane Reports is perfectly safe, and does not delete any Dataplane Reports user data or settings.
Dataplane Reports user data and settings are stored in an app-specific set of Active Objects tables in the Jira database, which are left untouched when Dataplane Reports is uninstalled. Upon reinstallation of Dataplane Reports, all app user data and settings are available again within Dataplane.
Security
Is Dataplane Reports vulnerable to CVE-2021-44228 Apache Log4j2 exploit ("Log4Shell")?
No. Dataplane Reports is not vulnerable to CVE-2021-44228, which is based on an exploit of the Java log4j2 (v2.0+) library.
Dataplane Reports does not use log4j2. For logging, Dataplane uses the log4j v1.2.17 API provided by Jira; but this log4j version is not vulnerable to CVE-2021-44228.
The Atlassian CVE-2021-44228 disclosure page details some specific circumstances in which a Jira instance, and apps like Dataplane Reports that use Jira's log4j v1.2.17 API, could be exposed to a CVE-2021-44228-like exploit should Jira be configured in a non-default way by an instance administrator. Please review that page in detail to determine if it applies to your Jira configuration.
...
| Anchor | ||||
|---|---|---|---|---|
|
Why is Dataplane Reports no longer available upon expiration of my paid license maintenance period?
If you are running Dataplane Reports 1.8 or lower, a bug in the Atlassian Add-On Manager (UPM) (UPM-4565) causes Jira to stop Dataplane Reports from running upon license maintenance expiration, rather than letting you continue using Dataplane outside of your maintenance period (as your perpetual license allows). This also affects impacts users who are in the process of upgrading from Dataplane Reports 1.8 or lower to a more recent release. We apologize for this inconvenience.
To resolve the issue while running Dataplane Reports 1.8 or lower, you will need to:
1) Upgrade to Dataplane Reports 1.9 or newer, and
2) Remove and reinstall your Dataplane Reports license. This will correct the licensing condition immediately.
If you are already running Dataplane Reports 1.9 or later, these special instructions do not apply and no action is needed.
To resolve the licensing bug, after upgrading to a new version of Dataplane Reports, visit the Manage Add-ons section of Jira Administration:
- Click on the Arsenale Dataplane Reports listing.
- Click the "pencil" icon next to the License Key text box to edit your existing license.
- Copy the Dataplane license string from the License Key text box to a temporary text file.
Delete your license string so that the License key text box is empty, and click Update.
- Paste your Dataplane license back into the text box, and click Update to apply it.
- Verify the License Status field shows your license is now "Valid".
...