...
If you're running Confluence Data Center, do ensure to add this parameter in all of your Confluence nodes.
| Info |
|---|
Confluence's Administration » Administration → General Configuration page has settings that would appear to change the applicable HTTP timeout, however, due to Confluence bug CONFSERVER-51594 Confluence gadget macros ignore these settings. For more details, see this Atlassian Knowledge Base article. You must instead use the JVM parameters listed below. |
...
To disable gzip compression, access the Jira administration panel select System » General → General Configuration » Edit → Edit Configuration, and then disable the "Use gzip compression" feature. Failure to disable Jira's gzip compression will result in Dataplane gadgets failing to display in Confluence.
...
Under any of the above circumstances, the new issues or custom field will not be available within Dataplane until you click on the Sync Index button on the Dataplane Reports → Administration page→ Configuration page.
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 | ||||
|---|---|---|---|---|
|
...
feedback and support links in Dataplane Reports?
Some Dataplane Reports includes a number of links in the application to allow users to easily open a support ticket: to suggest new features or product improvements, to request help with a feature or report, or to file a pages display links to our support portal, enabling users and administrators to easily suggest new product features or improvements, request help, or report a possible bug.
If See our documentation on Disabling Feedback and Support Links if you wish to disable this feature, hiding all product feedback links in Dataplane Reports:
Scroll down until you find the listing for 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 Dataplane Reports product feedback links are no longer visible to users.
...
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.
Licensing
...
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:
...
Delete your license string so that the License key text box is empty, and click Update.
...
.
| 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.