Release Notes

Lite v2.5.0 - 2025/05/06

[New] Dashboard: the app now defaults to show a dashboard with stats and insights!
Routine dependency updates.

[New] Dashboard: the app now defaults to show a dashboard with stats and insights!
[New] Classification: permission controls for whether to allow users to view classification levels, or allow users to specify classification level for their content.
Routine dependency updates.

[Improved] Content Audit: CPU and memory usage have been reduced by 50%+.
[Improved] Content Audit: issues archived by project now has archivedByProject status, which can be filtered. Due to Jira limitations, such issues cannot be purged by automation and the project would need be restored first.
Routine dependency updates.

[New] Policies: support multi-selection of entities when creating retention rules
[New] Classification: support multi-selection of entities when creating classification rules
[Improved] UI: improved response time
Routine dependency updates.

[Fixed] Content Audit: fixed time-outs when retrieving archived issues in some cases.
Routine dependency updates.

[Improved] General: migrated to the new @forge/kvs package for Forge Storage used for storing app configurations and other data.
[Improved] UI: descriptive error message upon network errors between browser and Atlassian
Routine dependency updates.

[New] General: in-app notification for new major versions.
[Improved] Audit logs: long entries now wrap short when expanded.
[Improved] Content Audit: precise prompt in empty state
[Improved] General: Tabs are re-ordered to follow user journey
[Fixed] Classification: the app can now set per-page classification level in content property after re-installation of the app. Previously the app will fail silently without setting the classification level if the page already has one set by a prior and uninstalled version of the app.
Routine dependency updates.

[Improved] Automation: Automation now runs on a daily basis instead of hourly. This change significantly reduces system load by leveraging the newly available long-running functions offered by the Atlassian platform.
Routine dependency updates.

[New] Classifications: added content classification support. Read more about the feature.
[Improved] UI: improved responsiveness and performance for text fields.
Routine dependency updates.

[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.

[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.

[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.

[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.

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.