How to use the Collaborative Editing Feedback Tool to provide problem reports
Purpose
If you experience serious problems with collaborative editing, such as data duplication, our Support team may ask help from users report problems and collect editing data. The plugin extracts data from the editor then matches it with page events and version history to create a complete snapshot of the lifecycle of the page. This data can assist our Support and development teams to identify low level issues in the editor.
You should only use the plugin when suggested by support, and should consider the files sensitive data.
What data does the tool collect?
When someone reports a problem, we collect all the changes that have happened to that page, including the page or blog history, any page events, and data from the collaborative editor (for the past 72 hours). The user reporting the problem will also be prompted to describe the issue in their own words.
Note: Synchrony captures every key stroke made in the editor when editing a page. For example if you type "The best ice cream is Vanilla
" and then backspace and change it to "Chocolate
", both "Vanilla" and "Chocolate" will be included in the Synchrony data.
This data is exported as a zip file, and saved to the following directory:
<shared-home>/collab-data/
if you run Confluence in a cluster<local-home>/shared-home/collab-data/
you are using non-clustered Confluence.
Because the collected data includes user generated content, generated reports are only kept for 5 days, then automatically deleted by the Clean up collaborative editing feedback reports scheduled job. A maximum of 200 reports are kept at any one time. You can change both of these values if necessary. See Configure the plugin.
How do I send this data to Atlassian?
The data collected is stored in your shared home directory. If you choose to share this data with our Support team for analysis, you can transfer the files through a support ticket. Do not share this data in any public locations, such as in Atlassian bug reports.
This data should only be provided when requested by a Support team member.
Using the plugin
Install the Collaborative editing feedback plugin
You need System Administrator global permissions to do this.
To install the Collaborative editing feedback plugin:
- Download the collaborative-editing-feedback-plugin-1.0.1.jar file.
- Go to Administration > Manage apps.
- Select Upload app and browse for the jar file.
Note: The tool will be bundled with Confluence in a future version.
Allow your users to self report problems
By default, the plugin only allows people with System Administrator global permissions to report problems through the administrative interface.
To allow users to self-report problems:
- Go to Administration > General Configuration > Collaborative editing feedback.
- Select Settings.
- Select the Allow users to report editor problems checkbox.
This will add the Report editing problems button to the header, when viewing or editing a page.
Report an editing problem
To report an editing problem from a page or blog post:
- Navigate to the problematic page or blog post.
- Select Report editing problems from the header.
- Enter any relevant information, such as what you were doing when the problem occurred.
- Indicate if you had recently copied and pasted data on the page, or if the page was updated externally (such as through the API, or by an app).
- Select Send feedback.
The report will be saved to the shared home directory, and will appear in the list of available reports (only accessible to System Administrators).
Report an editing problem by page ID
System Administrators can also generate reports for problematic pages using the page ID. This is useful if you don't want to allow users to self-report problems.
To generate a report for a particular page or blog post:
- Go to Administration > General Configuration > Collaborative editing feedback.
- Enter the page or blogpost ID in the
- Select Create dump button.
The report file will appear in the list of available reports.
Configure the plugin
You can change the default behaviour of the Collaborative editing feedback plugin using the following System Properties.
Property | Default value | Description |
---|---|---|
confluence.plugins.collab.feedback.destination.folder | <shared-home>/collab-data | Set this property to change where problem reports should be saved. For non-clustered installations, the default location will be <local-home>/shared-home/collab-data. |
confluence.plugins.collab.feedback.files.max | 200 | Set this property to limit the number of problem reports to store. |
confluence.plugins.collab.feedback.operation.timeout.sec | 20 | Set this property, in seconds, to change the operation timeout in seconds. |
confluence.plugins.collab.feedback.concurrent.max | 5 | Set this property to change the maximum number of concurrent data collection operations. |
confluence.plugins.collab.feedback.operation.format | csv | Set this property to change the format of the exported file. Can be csv or json. |
confluence.plugins.collab.feedback.cleanup.threshold.hours | 120 | Set this property, in hours, to change the length of time to retain reports. A scheduled job will delete any reports exceeding this limit, starting with the oldest. |