12th of July 2026 (patch release)

This article contains this patch release's bug fixes.

Bug fixes

• Fixed an issue where restoring criteria led to incorrect keyboard numbering in the new grading experience
  Previously, in some rare cases when removing and restoring criteria, the position would become wrong, causing incorrect numbering to be shown when using the new grading experience. Now, the keyboard numbering is always correctly shown.
   

• Fixed an issue with case insensitive comparison of the fill-in-the-gaps questions when using non-ASCII text
  Some fill-in answers that included special characters (for example letters with accents) were not always graded correctly when uppercase and lowercase should have been treated as the same.

  This happened because of the way those characters were compared during automatic grading. In some cases, the system could not match the student answer to the correct option, even when it should have. More information about this issue can be found here. 
   

• Fixed an issue where students would receive notifications of draft discussion replies
  Previously, if a reviewer saved a reply to a discussion as a draft, the student would receive a notification even though the reply had not been sent. Clicking the notification led to an "Access denied" page because the draft was not visible to them. Now, students are notified only after the reply is sent.
   
• Fixed an issue where the points in adjustments were still shown during the publication when "Points scored per question" was disabled
  Previously, When "Points scored per question" was disabled in the publication settings, the points per criterion and total points of the question were not shown. However the points in adjustment were still displayed. Now the points in adjustment are also no longer shown when "Points score per question" is disabled in the publication settings.
   
• Fixed an issue with creating assignments with an original_id through the API
  Previously it was possible for the synchronisation of an assignment to start too quickly, which resulted in the assignment settings being created twice. This could happen when an assignment was made through the API and contained an original_id to synchronize with. Now, this has been fixed, so that the creation of assignments with an original_id can no longer produce an error.