Release notes for version: 14.9.0

Technological stack

This section is important for Server solution. Cloud users need not worry about any of this.

• OS: Debian 12* on amd64 architecture
• Redmine: upgradable from version 5.1.8
• Ruby: 3.3.7
• Bundler: 2.3.7+
• Rubygems: 3.3.x
• Database: Percona/MySQL 8.x
• redis-server: 7+
• NodeJS: 22.13
• Docker engine: 27.3.1
• Docker compose: 2.29.7

Before every application upgrade, please carefully refer to all release notes between your existing version and the new version - there may be critical technical or functional changes explained.

*Debian 11 is still LTS, which means it is still supported by Debian creators. However, some new packages coming in the future will slowly but surely cease to work on Debian 11, which means there is no reason to unnecessarily postpone your OS upgrade.

Ruby and NodeJS are strictly mandatory, without these versions you will not be able to run Easy Redmine.

Or, forget about the management of technological stack and use Docker deployment. It combines the security of on-premises solution with nearly the comfort of cloud solution.

SLA System Overhaul for HelpDesk

We’ve reengineered the SLA (Service Level Agreement) system in Easy Redmine to improve accuracy, usability, and automation for your support workflows.

 Key Highlights

• SLA status now follows ticket status changes exclusively
  No more reliance on sending emails to affect SLAs—ticket status updates directly drive SLA logic and fulfillment.
• Improved fulfillment tracking
  First Response and Resolution SLAs are fulfilled by clear, system-driven events like the first status change or closing the ticket. Edge cases are smartly excluded to avoid false triggers.
• Suspended statuses fully supported
  Pausing tickets (e.g., "Awaiting customer info") suspends SLA timers and adjusts deadlines accordingly. If the ticket is closed while suspended, the SLA is marked as fulfilled from the pause point.
• More visibility with new SLA info on tickets
  Tickets now display SLA status, remaining time, total duration, deadline, and the exact fulfillment timestamp—dynamically updated and visible based on user roles.
• Refined SLA Events tab
  SLA events are now purely logs for investigation and tracking. Outdated fields will be removed after a transition period and replaced by new ticket-based data.
• Enhanced dashboards
  SLA data points like status, time remaining, and deadlines are available via dynamic filters. Remaining Time and Duration fields are now filled only after fulfillment (for closed tickets).
• Better API and integrations
  SLA data from dashboards is now accessible via the Tasks API and available in the Easy Redmine connector in the n8n marketplace.

These changes make SLA management clearer, more accurate, and easier to integrate with your workflows and dashboards.

Please view this explanatory demonstration where you will most clearly understand the benefits.

The SLA settings did not change and neither should your processes. The new feature is about a more intuitive and logical reporting.

Stabilization and security

The other changes are listed in the changelog, some are missing due to informational sensitivity. With every released version, we include improvements for stability and security.

Have you developed into Easy Redmine code? Please read on.

Version 15 (coming in autumn 2025) will require all code to be Zeitwerk compatible. Make your code compatible now by following the guide in the Developer's portal.

A brief summary:

1. Enable "zeitwerk mode" in your ENV
2. Check deprecations warnings
3. Follow our guide to fix them
4. Treat yourself to a reward

We sincerely recommend getting this over with when you have a little time. Your code will be modernized and ready for the new Rails generation. It will, of course, work on the current version as well.