Improved Features
Gmail Performance Enhancements
We are excited to announce that we have significantly improved the collection speed for data coming from Gmail. In a test environment we were able to reduce the collection and processing time for a large sample data set of Gmail data from 20+ hours to under 5 hours.
The best news? You don’t have to do anything differently. Your upcoming re-syncs for existing auto-sync Gmail sources will continue as set up but will now move faster as will any new syncs set up from this point on. The process for setting up a new Gmail sync is the same as it was prior to the improvements.
In order to ensure all customers have a smooth experience, these Gmail performance improvements will be rolled out to customers over the course of the summer months. To learn more visit Google Workspace: How to Connect and Collect
Enhanced Export Management
You are now able to change the name of an export after the export has been created from two places. First, you can change the name of any export from the list of exports on the ‘Export’ main page. The second place you can change the export name is on the detail page for the export. Having the ability to change the name of exports allows you to differentiate between exports easily. Learn more about How to Share and Manage Exports.
Additional Data Now Collected from Jira
We are now able to collect children issue information within Jira, such as the key, status, subject, and assignee of sub-issues in the parent issue. In addition, we are also now able to collect the history and work log sections from Jira issues. The ability to collect additional data from Jira allows for better discovery and data management.
Updated User Guides
Admin
Search
- Getting Started with Search in Onna
- Viewing Search Results in Onna
- How to Save and Manage Search Queries
- How to Use Filters
Connectors
- Confluence: How to Connect and Collect
- Jira: How to Connect and Collect
- Microsoft OneDrive Enterprise: How to Connect and Collect
- Microsoft Outlook Enterprise: How to Connect and Collect
- Microsoft Teams Enterprise: How to Connect and Collect
- Slack Enterprise: How to Connect and Collect
- Zendesk: How to Connect and Collect
- Zoom: How to Connect and Collect
Collecting and Processing
Exports
- How to Configure and Download an Export
- How to Share and Manage Exports
- How to Create and Manage Export Templates
Fixed Issues
Connectors
- This issue, when creating an auto-sync source in Jira, causing over-collection has been resolved.
- The issue in Slack Enterprise where users were unable to select channels for a custodian based collection has been resolved and you are able to create collections as intended.
- The issue in Confluence where users were unable to select ‘collect links’ and/or ‘from date’ in auto-sync mode has been resolved.
- The issue in Amazon S3 causing no additional resources to sync after receiving an error message has been resolved and data is syncing as expected.
- The issue in Microsoft Teams causing missing extensions in attachments has been resolved.
- The issue with disrupted syncs in Confluence has been resolved.
Export
- The issue causing Group IDs to be missing from exports has been resolved.
- The issue, when exporting neighboring Slack conversations, causing the same document to be exported multiple times, has been resolved.
- The button to re-enable a download for exports has been removed from all members other than the creator of the export.
Platform
- The issue causing Onna account owners the inability to delete workspaces not created by them has been resolved. Onna account owners are now able to delete workspaces not managed by them.
- This issue where case sensitivity in usernames was affecting the user’s ability to access shared workspaces/collections and add Admin Credentials has been resolved.
Search
- The issue where a condition could not be updated when editing an advanced search has been resolved, and you can now manage advanced searches as expected.
- The issue causing search issues with preservations has been resolved, and you are now able to search preservations as expected.
- The issue where searches on boolean (true/false) fields were returning too many results has been resolved.
- This issue causing “to/from” details to be missing from the details panel of a file has been resolved, and all file details are displaying correctly.
- The issue causing smart alert queries with tag conditions to fail has been resolved, and alerts are now working as intended.
- The issue causing saved search queries to fail loading has been resolved.
- The issue causing all search result files to display in PDF format by default has been resolved.
- The issue causing queries for tags ending with numbers to fail has been resolved, and all results containing tags are now displaying appropriately.
- The issue where users are unable to save a search due to case sensitivity issues has been resolved.
Comments
0 comments
Please sign in to leave a comment.