This item has been included in the 1.1.0-rc1 and rolled to UCD staging in preparation for production release.

Closing since this is a QA pass.

I've created and linked a new JIRA for the issue David notes.

It no longer continues to drop lowest with the items set with unequal points and weight by points option selected.

my sequence of actions was

1- start from existing gb with weighted categories mode

• with existing category with drop lowest specified and equal weight items option selected

• with multiple existing items with equal points and equal weights

• with drop lowest working as expected and 1 grade in the category is marked as dropped.
  2 - edit the category and select the weight by points option and save

  • equal weights option dissappears

  • no changes visible in data spreadsheet - lowest grade still shows as dropped.
    3 - edit item and change points to a different value, then save

  • gets a pop-up about rescaling scores – say yes. ***

  • data spreadsheet changes – no scores dropped.

In the spreadsheet, there is no drop lowest entry marked, whole there are items of unequal points.
once all the items are changed to the same new points value, the drop lowest reappears in the data spreadsheet.

QA PASS

•  

  •  

    • I notice that the pop-up about rescaling results in a save being treated as a save/close – the edit page disappears, uncovering the spreadsheet.

QA ENVIRONMENT -
vista enterprise, firefox, ie7
smartsite-test sakai_2-5-x-test-076 - Sakai 2.5.x-R57934 gb2-1.1.0-b2 - Server sakaitest2

QA SUMMARY -
site xxx 123 123
BUG -discovered during testing this... weigh by points does not hold during creation grbk-352
1 - added "weight by points" category, selected equal weight items...
note - if you check equal weight items, then weight by points, the equal weight items box disappears.
uncheck weight by points and equal weight comes back. now you can enter a drop lowest number. entered 1.
2 - graded items @ different point values (but defined as equal weights) and drop lowest works appropriately.
eg: drops an item 49/50 over an item of 99/100. drops 49.5/50 over 99/100...played w/assorted scores and drops made sense.
3 - edit cat and now select weight by points. drop lowest and =wt items boxes disappear.
4 - nothing shows now as dropped and %category values have changed for all items to reflect point values.
50 point item is now 20% and 2 100 point items are 40% of category - ok
5 - then unchecked weight by points and re-selected =weights. drop lowest 1 came back and items are again
dropped by scores appropriately.

once you figure out HOW it works, it does work correctly.

QA RESULTS -
it works as I expect BUT I'm not going to pass it because I didn't do EXACTLY what David did to come up with the JIRA.
David needs to repeat whatever he did yesterday and ensure that it's a pass for him.

he said something about starting with a categories site and switching to weighted categories. so he introcuded a
number of variables/oddities that I didn't because I don't know WHAT he did. so he should be the definitive one to
determine if this is REALLY fixed as he knows what he did in the first place
make sense?

This item is now ready for testing.