Skip to content

Redmine SLA 3.4.1

Choose a tag to compare

@likehopper likehopper released this 08 Nov 09:07
· 37 commits to main since this release
5b4ba4b

Issues whose priority (or SLA custom field value) was deactivated show their SLA priority, term and respect again: the columns were empty while the respect filter still counted them.

When two levels of one SLA use calendars opening at the same minute, the level with the lowest id now always wins, so an issue no longer switches level on a refresh.

Local holiday names are requested from nagerholidays.com, the official Nager.Date host, instead of date.nager.at, which already redirects its home page there. One outbound HTTPS host is now enough. The release also removes dead code and stops listing cache refresh under view_sla (it already required manage_sla; access is unchanged).

Validation: Redmine 5.1.13, 6.1.4 and 7.0.1 on PostgreSQL 17.7, MariaDB 10.11.19 and strict MySQL 8.0.46: 10,788 tests / 68,332 assertions, no failures or errors, 12 expected PostgreSQL-only skips. The upgrade from 3.4.0 was checked on all nine combinations, and a live import call returned French public holidays in English and local names.

Upgrade: update the plugin files, run bundle exec rake redmine:plugins:migrate RAILS_ENV=production (migration 027 redeploys sla_get_level), then restart Redmine. Existing caches are kept: refresh or purge them to apply the level rule to issues already cached. Allow outbound HTTPS to nagerholidays.com. No production deployment was performed.

Changelog · Testing · Public holiday import · Pull request #91