Release v3.0.1 – Migration to Forge on Connect

This version marks a significant technical milestone as we begin the transition to Atlassian Forge. The app now runs on Forge using Connect as a remote backend and UI served via Atlassian Connect Express. This hybrid model allows seamless updates for users, setting the foundation for a full Forge migration in future releases.

New Features

• Added improved validation for POST and PUT requests.

• UI updated for a more polished and consistent user experience.

• react-table removed and replaced with @atlaskit/table-tree for all table components.

• User names are now displayed in cancelled template information.

• Introduced scripts and infrastructure for Forge deployment, including pipeline and environment configuration.

• Caching flush implemented on deployment to prevent outdated data.

• Improved search logic for rules, allowing better filtering by name.

Fixes & Improvements

• Addressed a Regular Expression Denial of Service (ReDoS) vulnerability by using RE2 for regex validation.

• Refactored export functionality for better performance.

• Resolved multiple UI bugs in templates and dialogs.

• Fixed missing rule creation when new templates are created.

• Resolved issues with delete dialogs in the Data Cleaner module.

• Enhanced error handling and improved search process stability.

• Fixed an endless search loop and added logging and test coverage.

• Corrected behavior when updating clientKey values.

• Fixed announcement validation errors.

• Fixed pagination issues in user announcements and removed legacy caching.

• Replaced custom concurrency logic with p-limit and added fallback improvements.

• Fixed incorrect updates in statistics after user responses.

• Resolved CQL search issues related to request headers and rate limits.

• General codebase improvements including TypeScript migration, module separation, and logic cleanup.