Hot-fix 3.40.6 Managua

Resolved issues

• Resolved issue of enumerators not having the right permissions to see the results page for private projects #3457

• Fix problem with CronJobs not running in k8s #3455

RSR release 3.40.5 Managua hot-fix

Resolved issues

• Fix problem with start and end dates for report generation being incorrect in some browsers #3444

RSR release 3.40.4 Managua hot-fix

Resolved issues

• Fix errors with the Overview/Full-view button on the results page after creating a new update #3382

RSR release 3.40.3 Managua hot-fix

Resolved issues

• Fix performance problems related to indicator dimensions #3420

RSR release 3.40.2 Managua hot-fix

Resolved issues

• Fix warning about missing Google maps API key for maps on the project page and in the widgets #3407

RSR release 3.40.1 Managua hot-fix

Resolved issues

• Org. admins are now able to edit updates created by users which they can administer #3400

• Fixed incorrect error message about results having no quantitative indicator, before doing an IATI export #3392

Code maintenance

• Sped up generation of serialized data by the ProjectUpdateSerializer #3293

RSR release 3.40 Managua

New and noteworthy

• Password enhancements #3357

• Indicate projects as private in the project CRUD page as well #3294

Resolved issues

• Map was zoomed in one level too much #3327

RSR release 3.39.4 Belmopan hot-fix

Resolved issues

• Project access header removed from the User Management page - this feature is still in Beta #3380
• Pagination works correctly on the Project update and Organisation directory pages #3371

Data maintenance

• Script to remove default periods from Indicators in single hierarchy projects has been added #3383
• Script to check EUTF core results for errors and notify specified users has been added #3374

RSR release 3.39.3 Belmopan hot-fix

Resolved issues

• Now using react-datepicker for the 'Project Update' event date field so that it works correctly in all browsers #3367

RSR release 3.39.2 Belmopan hot-fix

Resolved issues

• Google maps API requests now use an API key to avoid showing a 'for development purposes only' watermark #3368