The release notes provide information on the features and improvements in the specified version. The release dates related to the versions are published in the Evaluation release schedule.
Improvements
New functionality, user experience refinements, and bug fixes. Issues marked as hotfix are developed in this sprint but applied to the previous release or directly to production, depending on impact.
Usage of global and personal feedback in External Examiner should be consistent - EV-438
The External Examiner questionnaires offer two options to deliver feedback on the examined specification or programme. It was found that the different options, usage and related effects for delivering feedback were not clear for the users, not clear enough in the system.
Let's first start with a more in-depth clarification, and then define the change applied, and it's possible effect.
For a specification or programme-level evaluation, there can be one or more External Examiners as participants. Each EE completes their own questionnaire and only sees their own responses. The Programme Leader can then view these responses through the configured report, selecting the relevant participant where there is more than one EE.
An EE can provide two types of feedback:
Participant feedback – feedback specifically intended for the selected EE.
General feedback – feedback relating to the specification/programme evaluation as a whole, which should be the same regardless of which participant's report is being viewed.
What we have found (bug)
We have identified an issue with the general feedback field shown within the report.
Although this field is presented and intended as general feedback, feedback entered there has in fact been stored against the participant whose report was being viewed at the time. This means that, for an evaluation with multiple EEs, different "general" feedback may currently exist for each participant.
That is not the intended behaviour, and we are fixing this bug.
Depending on permissions/configuration, users may also have access to a separate Feedback tab, which contains the general feedback field. This means users could effectively encounter two places that appeared to be for general feedback, causing interpretation / usage issues.
What we are changing
We are making two changes so that the workflow is clearer and consistent going forward:
- The general feedback field in the report will become genuinely general. It will no longer depend on which participant's report is being viewed.
- In a next release an option will be added to hide the separate Feedback tab for users. This will allow the report itself to be the single place where EE responses are reviewed and provide both participant-specific and general feedback.
This should give us a much more straightforward workflow and a stable configuration to use going forward.
Action:
Due to the bugfix, it could be that feedback meant as 'generic', has been stored as 'participant'. The change will store and show the data in the correct location, which could mean that the 'generic' intended information is not shown on the report. The possible effected customers will get a message from Support team, to provide more information and a request if reports are effected and what we can do to assist.
Security
An integral part of our development and build process is the automatic scanning for known security vulnerabilities. Fixes are prioritised based on impact: some may require an immediate hot-fix, while others are addressed in the current or next Sprint (release). For more information on reported vulnerabilities, see the central database of vulnerabilities.
Implemented security fixes - EV-437
Based on our daily running security validation, the used libraries with either a critical or high reported vulnerability have been evaluated for impact (false positive validation) and based on the result updated.
Refer to the Evaluation manual for configuration guidance.