Gradebook multiplying points when grades are attached to it from other tools.

Description

Issue with attaching grades directly to Gradebook (1 & 2) from both the "Tests & Quizzes" tool and the "Discussion & Private Messages" tool. Gradebooks multiply (usually by 10) random students' grades in random assessments. Current issue workaround is to detach and reattach the assessment to and from Gradebook (1 & 2).

How to fix.

Fortunately, a second bug (or perhaps oversight) is that in the original Gradebook, you can still edit a grade even if it came from a tool (GB2 locks you out of editing grades sent from other tools). So, just change all the numbers back to their original values (8000 was originally 80, 8.0x10 to the 15 was original 80, etc).

Attachments

2

Activity

Show:

Derek Ramsey April 22, 2013 at 1:16 PM

Verified on Sakai 2.9.2-rc01 (Kernel 1.3.2-rc01)

Oliver Williams March 27, 2013 at 10:40 AM
Edited

Verified in sakai/trunk on Oracle - Built: 03/27/13 08:00 - Sakai Revision: 121821 (Kernel 1.4.0-SNAPSHOT)- Server sakai-nightly.uits.iupui.edu on GC25.01 and IE8.0.6

Sree Chandra March 22, 2013 at 10:18 AM

Verified it on http://nightly2.sakaiproject.org:8082/portal Looks like the issue is fixed. Working fine.

Bryan Holladay March 22, 2013 at 9:39 AM

Strange

Anyways, yea, break it up into two jiras: msgcntr & samigo The msgcntr one is completed and in trunk and 3.0.x.

Neal Caidin March 22, 2013 at 9:36 AM

Well, I believe you, but I cannot reproduce the problem on https://qa29.longsight.com - "TRUNK - Sakai 2.9.1 (Kernel 1.3.1)-"

I followed your instructions. I went to Gradebook Setup and chose Percentages. I had student0001 post a message to General Discussion forum. I had instructor role go to Statistics and Grading button. Then I chose Statistics and Grading by Topic. Then I entered in a score several times. But it correctly overwrote the score and only used the last one in the Gradebook.

I see you've already merged your fix so it will get into 2.9.2 . That's cool. Not sure what to do with this ticket status though. What if we moved it to MSGCNTR and set it to verified with a merge flag of Resolved?

But then there is also the report of the same problem in Samigo, so that needs to be tracked.

Fixed

Details

Priority

Affects versions

Fix versions

Components

Assignee

Reporter

Labels

Created February 4, 2013 at 12:20 PM
Updated October 4, 2013 at 1:08 PM
Resolved March 22, 2013 at 9:53 AM