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

Grade modified timestamp sometimes is not set correctly

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a bug
    • Icon: Minor Minor
    • None
    • 3.1, 3.2
    • Assignment
    • None
    • MOODLE_31_STABLE, MOODLE_32_STABLE
    • Hide

      1. Create an assignment within a course with 1 teacher and 1 student.
      2. As a student, just access an assignment.
      3. Check that a new record in assign_submission was created. Notice the timemodified timestamp.
      4. As a teacher, go in to assignment grading view, navigate to the new grading interface for that student.
      5. Check that a new record in assign_grades was created. Notice timecreated and timemodified values. They're different, timecreated > timemodified, and g.timemodified === s.timemodified.

      Show
      1. Create an assignment within a course with 1 teacher and 1 student. 2. As a student, just access an assignment. 3. Check that a new record in assign_submission was created. Notice the timemodified timestamp. 4. As a teacher, go in to assignment grading view, navigate to the new grading interface for that student. 5. Check that a new record in assign_grades was created. Notice timecreated and timemodified values. They're different, timecreated > timemodified, and g.timemodified === s.timemodified.

      There are some strange issues going on with assign_grades records. Sometimes it takes assign_submission.lastmodified timestamp and saves it as assign_grades.lastmodified, thus generating faulty 'requires grading' reports. It can even be the case when assign_grades.timecreated is bigger that assign_grades.lastmodified!

            Unassigned Unassigned
            pavel.m.sokolov Pavel Sokolov
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.