Release Notes
v3.14.0 - 2024/12/08¶
- [New] Classifications: added content classification support. Read more about the feature.
- [Improved] UI: improved responsiveness and performance for text fields.
- Routine dependency updates.
v3.13.0 - 2024/11/08¶
- [Fixed] Automation: Fixed an issue discovered during internal scaling tests where platform authentication could expire during automation tasks for extra-large instances. This issue had not been encountered in production. The app now handles authentication expiry correctly, ensuring uninterrupted automation.
- Routine dependency updates.
v3.12.0 - 2024/10/24¶
- [Improved] Automation: improved speed for automation execution.
- [Improved] Content Audit: improved UI performance during loading
- Routine dependency updates.
v3.11.0 - 2024/09/28¶
- [New] Policies: Added support for specifying a time frame per retention rule. If defined, only content created or last modified within the time frame will match the rule.
- [New] Policies: Added the ability to disable automation per policy.
- [New] Policies: You can now choose between "Created" or "Last Modified" as the trigger for the retention period on a per-policy basis.
- [New] Policies: Added an optional
Code
field to identify policies. - [Improved] Policies and Automation: Enhanced help messages in the Policies and Automation tabs.
- [Improved] Content Audit: Search functionality now includes policy name and code.
- [Improved] Automation: The purge delay can now be set to 0 days (previous minimum was 1 day).
- [Fixed] Audit Log: The summary tag line now correctly handles empty states.
- Routine dependency updates.
v3.10.0 - 2024/09/09¶
- [New] Policies: Retention rules now support associating a policy to a user. Issues that are created or reported by the user will be applied with the associated policy. User-based policies takes precedence over project-based rules and the default retention.
- [New] Policies: A new preset policy is added with 100-year retention period for Litigation Hold. Note that only new installation of Content Retention Manager for Jira will see this new preset policy. Existing customers can manually add a policy to the same effect.
- [Improved] Content Audit: Filters dialog now requires at least one content type, one content status, and one retention status to be selected, to avoid unintended empty filter results.
- [Fixed] Policies: The Entity column of Retention Rules now shows the project ID instead of blank if the information of the project has not been loaded yet.
- [Fixed] Policies: The title of the dialog for add or update retention rules has been corrected. Previously it mistakenly says add or update policies.
- Routine dependency updates.
v3.9.0 - 2024/08/27¶
- [Improved] Audit Logs: loading audit logs is now 5x faster
v3.8.0 - 2024/08/09¶
- [Fixed] Content Audit: selection change should update available actions
- Routine dependency updates
v3.7.0 - 2024/07/10¶
- [Improved] Content Audit: always show ID in tooltips for contents in trash
- [Fixed] Content Audit: select-all checkbox now selects only contents visible in the table
- [Fixed] Automation: acknowledging a warning is no longer retained if changes are made again during the same browser session. Separate acknowledgement is no required.
v3.6.0 - 2024/06/24¶
This is the initial public release of Content Retention Manager for Jira. Key features include:
- Content Audit of Jira issues retention status with filtering, sorting, and searching
- Policy Management. Set your team's retention policy with a global policy and granular policies that can be associated with individual projects.
- Automation allows for the active removal of Jira issues outside of the retention period.
- Audit Log allows you to see when and by who polices are updated and when content is removed by automation.