Skip to content

v3.1.1

Choose a tag to compare

@likehopper likehopper released this 18 Oct 00:57
· 274 commits to 932b743ee2e1014d56b6de3929c189be8d25ff9e since this release

3.1.1 stops SLA calculation on projects whose SLA module is disabled and makes update_sla apply its options.

  • Projects without the SLA module get no SLA level: their cache is purged and no longer rebuilt, and their project-tracker configuration is kept for a later re-enabling. The issue "Explain" view lists no SLA level for them.
  • update_sla processes all projects by default and gains projects=[all,with_sla,without_sla], e.g. projects=without_sla to only clean up the cache.
  • update_sla now applies its scope option, previously ignored: inprogress (default) updates open issues and closed issues not updated since their closing, miss only issues without SLA cache, all every issue. scope=miss no longer aborts with SCOPE ERROR.
  • update_sla keeps the SLA cache of projects that are not active (closed, archived) instead of purging it.

Validation: all five suites passed on Redmine 5.1.13, 6.1.4 and 7.0.1, each with PostgreSQL 17.7, MariaDB 10.11.19 and strict MySQL 8.0.46: 1,069 tests per combination, 9,621 total, zero failures/errors/skips. Migration 202111112021021 rolled back and reapplied on every combination. Exact runtime details: doc/TESTING.md.

Upgrade: back up the database, update the plugin, run bundle exec rake redmine:plugins:migrate NAME=redmine_sla RAILS_ENV=production, then restart Redmine. Migration 202111112021021 makes sla_get_level return no level for projects without the SLA module. Then run rake redmine:plugins:redmine_sla:update_sla RAILS_ENV=production once to purge the SLA cache left on projects without the SLA module.

No production deployment or representative performance benchmark was performed.