You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the old user isn't just deactivated, but split out of the group and then removed from the assignment a third issue gets introduced:
files uploaded by the user are still visual, but trying to download them or generating a Zip file for the assignment both causes a FileNotFoundError. Re-merging the old user to the group doesn't solve the issue.
Sticking to the old 'merge into' procedure will prevent this from happening from future username switches, but the issue still holds for other scenarios involving group changes, and we should probably handle it better than a 500 error.
Solution A
when an student with files is removed from ('split out of') a group an addition warning listing the file info (names, dates and size) should be displayed, warning that the files could become unavailable for the remaining students if the user later gets removed from the assignment.
when a student group (of 1 or more students) is removed from an assignment, also check if that effects other other student groups and if so remove their clickable link and add a strikethrough effect to them.
Solution B
rework how student group file ownership works to prevent this issue overall.
The text was updated successfully, but these errors were encountered:
Description
Awaiting a proper 'merge into' option (issue #1122) we have solved mid-semester username switches by the following procedure:
This procedure is time-consuming, error-prone, and creates additional issues:
waiting for feedback
due to issue Assignment status still masked for some assignment groups #1101.If the old user isn't just deactivated, but split out of the group and then removed from the assignment a third issue gets introduced:
FileNotFoundError
. Re-merging the old user to the group doesn't solve the issue.Sticking to the old 'merge into' procedure will prevent this from happening from future username switches, but the issue still holds for other scenarios involving group changes, and we should probably handle it better than a 500 error.
Solution A
Solution B
The text was updated successfully, but these errors were encountered: