Name |
Last commit
|
Last update |
---|---|---|
.. | ||
oa_base.js | ||
oa_container.js | ||
oa_grade.js | ||
oa_peer.js | ||
oa_response.js | ||
oa_self.js | ||
oa_staff_info.js | ||
oa_training.js |
This corrects an issue where assessments were sometimes incorrectly associated with the wrong response. The behavior was caused because the POST request to the `peer_assess` handler only contained the feedback text/options and did _not_ include mention of which original response was being assessed. If the current workflow item is updated on the server _after_ the page first loads but _before_ the page is submitted, this submission will be incorrectly associated with the following response. Steps to reproduce: - Submit a response (User A). - Wait for peers to submit responses (User B and User C). - Load page with first peer response to be assessed (not not submit). - Open the same page again in a new tab. - In 1st tab, assess and submit assessment for User B. - In 2nd tab, assess and submit assessment for User B. - Notice that your assessment for User B's response is also applied to User C's response. This changeset does _not_ restore data retroactively. Fix TNL-680
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
oa_base.js | Loading commit data... | |
oa_container.js | Loading commit data... | |
oa_grade.js | Loading commit data... | |
oa_peer.js | Loading commit data... | |
oa_response.js | Loading commit data... | |
oa_self.js | Loading commit data... | |
oa_staff_info.js | Loading commit data... | |
oa_training.js | Loading commit data... |