Most sprints we release a lot of new user or administrator related functionality.
During these standard Sprints we always do some technical issues, that will not be noted in the release notes unless it's a security update or may have impact on the application behaviour / interfaces.

‍
This sprint we didn't develop much user-oriented functional features. We mainly focussed on improving the application infrastructure and architecture. From a product functional perspective not interesting, but for the longer run these technical sprints focus on improving quality of releases, guarantee usage of future proof libraries/components for development.

‍

New features and improvements

BUG - Fixed: Preview of lecturer question block - EV-196

Resolved an issue where the preview of the lecturer question block didn't work correctly in case the sidebar-option was selected. Since the sidebar in preview of a single page (block) is not useful, the sidebar will not be shown on individual previews. For the complete evaluation preview, the sidebar will be shown (in case it is configured to be shown).

‍

BUG, USABILITY- Fixed: Preview of lecturer question block - EV-195

Last release we introduced the visual enhancement in the sidebar evaluation navigation to show the status of each page (questions answered, question required, ...). In a situation where an already answered evaluation was 'reopened' the calculation of the answers was reset to 0. This has been fixed, so the original answers are taken into consideration displaying the page questions status.

‍

USABILITY- Calculation of open questions should not include informative questions - EV-194

Related to the issue above, we improved the calculation of the total number of questions on a page. The informative question type is actually not a question, but allows to place any text or other information between the actual questions. The informative questions were also in the calculation of the questions on a page. This has been changed, so the informative question is no longer part of the calculated questions value.

‍

Security improvements

For the third time this year we had a sprint (release) with no security fixes.
This is breaking the trend of having a security fix in each sprint (release), like we had last year.

Check the central database of vulnerabilities for detailed information on each CVE.

‍

‍