Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-25526

Random Allocation does not properly balance workload when Manual Allocations already exist

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.0
    • Fix Version/s: 2.0.2
    • Component/s: Workshop
    • Labels:
      None
    • Affected Branches:
      MOODLE_20_STABLE
    • Fixed Branches:
      MOODLE_20_STABLE

      Description

      When some students have already been manually allocated to review other students' work, Random allocation fails to incorporate this information properly, resulting in an unbalanced workload amongst students.

      Steps to reproduce:

      Given a sample Workshop of five students in which all five students have submitted responses:
      1. Manually allocate some students. In my case, I allocated: two students to mark one submission, one student to mark two submissions; two submissions with one marker, one submission with two markers.
      2. Click Random Allocation.
      3. Allocate 3 reviews per submission, being sure not to remove current allocations.
      4. Check the allocations on the Manual Allocation page.

      Expected results:

      Each submission should have three reviewers, and each student should be reviewing three submissions (balanced workload).

      Actual results:

      Each submission has three reviewers, but one student has four reviews, and another has only two. This is not a balanced workload.

      Notes:

      Please note that due to the random element of the allocation alogrithm, this may not be reproducible every time. However, I have reproduced it three times in a row, each time with different manual allocations. I don't think reproducing it should be especially difficult.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  21/Feb/11