Issues

 
2 of 2

Auto-submit always sends last score which can allow zeros to override scores on multiple submissions in various cases

Fixed

Description

There's a grading issue where zeroes can overwrite good scores even for highest score. In my research autosubmit will only always submit the last (current) score to the gradebook. There is some logic to have it not submit a score to the gradebook in the highest score case, but no consideration for average score. There are a few ways to replicate this. All involve multiple submissions with auto-submit running at the end. Either on the end of the initial run or any time an instructor modifies the dates and gives students more time.
 
See test plan for full steps to test this.

Attachments

1

Details

Priority

Affects versions

Fix versions

Components

Assignee

Reporter

Labels

Created November 7, 2014 at 2:44 PM
Updated October 10, 2018 at 12:38 PM
Resolved March 6, 2018 at 12:00 PM

Activity

Sam OttenhoffOctober 10, 2018 at 12:38 PM

Seems like this change causes auto-submit to overwrite good event log data ....

Derek RamseyMarch 16, 2018 at 3:19 PM

Tested on 11x with due and retract date.  Both were submitted when autosubmit job completed.  Also verified the average and last scores were submitted to gb properly when autosubmitted.

Matthew JonesMarch 15, 2018 at 6:55 PM
Edited

Okay this should be on the 11.x nightly server as of tomorrow (3-16). I'd be cool if someone could check it out there. At least verify the auto submission case is working.

Tiffany StullMarch 13, 2018 at 8:06 AM

Dates really need to function more like timers, so that work saves at the latest submission date if the student is still in the process of working on a test at that date (instead of it looking like they can continue working on the test when they can't), but it would require a total rewrite of due/late submission functionality.  Anyway, a discussion for another JIRA ;).

Matthew JonesMarch 13, 2018 at 8:00 AM
Edited

Yeah, auto-submit cannot save because it's not on the client. And currently by default auto-submit isn't even scheduled to run so every school may have a different experience depending on their schedule. Some schools only run auto submit once a day, some every hour some possibly more often. The point is really just to catch anything that didn't get submitted so too frequently running this shouldn't catch anything, but it's not going to submit any answers for the user, that's only in the client.

I don't know if the code for autosubmit checks the timer at all but maybe that could be incorporated. There were those UVA fixes for the timer to make it more reliable which might also reduce this as a problem.

As long as all methods send the "correct" score to the gradebook, that was what all this issue fixed. Perhaps a better solution in the future could be if auto submit was ever turned on by default, it could handle submission of the timed assessments. The timer would just mark them as complete and ready to autosubmit. But nobody has set this up yet. Maybe for 13.