Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-44446

Samigo: Revert SAK-44320 AutoSubmit Event Log submitted date change - if desired, add new column

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: OPEN
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 19.6, 20.1, 21.0, 22.0 [Tentative]
    • Fix Version/s: None
    • Labels:
    • Test Plan:
      Hide

      Testing:

      1. Create a site with at least 2 students and Tests & Quizzes.
      2. Create and publish 4 quizzes with at least one question and the following settings, giving yourself sufficient time between due and late submission dates to submit both before and after the due date:
        • Quiz 1: Due date, no late allowed, time limit
        • Quiz 2: Due date, late submissions allowed, time limit
        • Quiz 3: Due date, no late allowed, no time limit, autosubmit enabled
        • Quiz 4: Due date, late submissions allowed, no time limit, autosubmit enabled
      3. As Student 1, submit each quiz manually before due date.
      4. As Student 2, start each quiz, save and leave it before due date.
      5. As Student 3, start each quiz that allows late submissions after the due date but before the late submission date. Save your work and leave it before the late submission date.
      6. As instructor, edit settings on Quiz 3. Add a date/time exception for Student 2 to enable a late submission date just for that student.
      7. Log in as Student 2 and start Quiz 3. Save some work but don't submit. Leave the quiz.
      8. Wait until the latest of the quizzes' late submission dates has passed.
      9. Log in as admin and run auto-submit job in Job Scheduler.
      10. Log in as instructor and review the Event Log. Expected results:
        • Submitted date is always the date when the quiz was actually submitted (either by manual, timer submit, or auto-submit.
        • If change is made to add Last Saved column, column indicates date of last save either by student, timer, or auto-save process.
        • For student with exception, the exception date should be the auto-submit date.
        • Errors column should indicate No Errors (method of submission), i.e., "No Errors (User submit)", "No Errors (Timer submit)", or "No Errors (Auto submit)".
        • Duration column should indicate how much time elapsed between when the site participant began taking the assessment and when it was actually submitted, rounded up to the nearest minute.
      11. Review Scores page for each quiz. Expected results:
        • Submit Date column shows last saved date.
        • When started after due date, submit date is marked with LATE text.
        • When auto-submitted, submit date is marked with AUTO-SUBMIT text (both LATE and AUTO-SUBMIT should be indicated for submissions that were both started late and auto-submitted).
      Show
      Testing: Create a site with at least 2 students and Tests & Quizzes. Create and publish 4 quizzes with at least one question and the following settings, giving yourself sufficient time between due and late submission dates to submit both before and after the due date: Quiz 1: Due date, no late allowed, time limit Quiz 2: Due date, late submissions allowed, time limit Quiz 3: Due date, no late allowed, no time limit, autosubmit enabled Quiz 4: Due date, late submissions allowed, no time limit, autosubmit enabled As Student 1, submit each quiz manually before due date. As Student 2, start each quiz, save and leave it before due date. As Student 3, start each quiz that allows late submissions after the due date but before the late submission date. Save your work and leave it before the late submission date. As instructor, edit settings on Quiz 3. Add a date/time exception for Student 2 to enable a late submission date just for that student. Log in as Student 2 and start Quiz 3. Save some work but don't submit. Leave the quiz. Wait until the latest of the quizzes' late submission dates has passed. Log in as admin and run auto-submit job in Job Scheduler. Log in as instructor and review the Event Log . Expected results: Submitted date is always the date when the quiz was actually submitted (either by manual, timer submit, or auto-submit. If change is made to add Last Saved column, column indicates date of last save either by student, timer, or auto-save process. For student with exception, the exception date should be the auto-submit date. Errors column should indicate No Errors (method of submission), i.e., "No Errors (User submit)", "No Errors (Timer submit)", or "No Errors (Auto submit)". Duration column should indicate how much time elapsed between when the site participant began taking the assessment and when it was actually submitted, rounded up to the nearest minute. Review Scores page for each quiz. Expected results: Submit Date column shows last saved date. When started after due date, submit date is marked with LATE text. When auto-submitted, submit date is marked with AUTO-SUBMIT text (both LATE and AUTO-SUBMIT should be indicated for submissions that were both started late and auto-submitted).

      Description

      SAK-44320 introduced a change to the behavior of the Tests & Quizzes Event Log, to show the last saved time in the Event Log for auto-submitted tests instead of the actual time of submission. The actual time of submission is critical to have available in the UI both for instructors who are concerned about when a submission occurred and for support teams troubleshooting student submission issues.

      SAK-44320 needs to be reverted as it is a bug to show a false Submitted Date.

      If it is desirable to indicate last saved time in the Event Log, this needs to be added as a separate column for Last Saved.

      Note that the last saved time will always indicate the same time as the submission (for manual and timer submits); it will only differ from the Submitted Date in the event of auto-submits.

        Gliffy Diagrams

          Zeplin

            Attachments

              Issue Links

                Activity

                  People

                  Assignee:
                  maintenanceteam Core Team
                  Reporter:
                  rainribbon Tiffany Stull
                  Votes:
                  0 Vote for this issue
                  Watchers:
                  7 Start watching this issue

                    Dates

                    Created:
                    Updated:

                      Git Integration