Exception's Retract setting not 100% transparent - Uses "Yes, until" setting when not set
Description
Environment
Test Plan
1)-Setup test with "Yes, until" setting in the past.
-Set an exception in the future for a specific group or student without retract setting
-Student should see the test. ?If this is the desired result?
2)-Setup test with "Yes, until" setting in the future.
-Set an exception in the past for a specific group or student without retract setting
-Student should not see the test. ?If this is the desired result?
is duplicated by
is related to
relates to
Activity
Mark Golbeck August 27, 2024 at 8:23 AM
Since it's been over two years without any further information provided, we're closing this Jira issue for now. If more details become available in the future, we can reopen it. Thank you.
Tiffany Stull April 29, 2021 at 4:21 PMEdited
One of the proposed fixes in is to make the Exceptions date handling behave identically to the overall assessment date/time limit handling. For example, assuming is fixed:
When you select the "Exception for User" or "Exception for Group" field, date and time limit fields should pre-populate from overall assessment dates.
When a due and/or retract date is present, it should be exposed to the user in the UI while setting the dates and in the Existing Exceptions table.
You should also be able to set a null due and/or retract date for exceptions to make the availability for the excepted user unlimited (or unlimited for late submissions).
I believe that would cover the issues mentioned here.
Tiffany Stull December 4, 2017 at 11:02 AM
The *Retract Date* is the final close date for a quiz. In Sakai 10, the display of the retract date on the user side was changed to *Late submissions accepted? Yes/No* because instructors were often confused by the terminology _Retract Date_.
Additionally, in Sakai 10.4 (I think - maybe a later 10 dot version?) the *user-facing behavior was modified so that when you indicate *Late submissions accepted - No, the Retract Date* is hidden from user view (although it is still acting on the test, it's just the same as the *Due Date). In earlier Sakai versions, a manually-entered *Retract Date* was required to use *Autosubmit*.
The problem with the Exceptions is that leaving the *Late submission date* field empty is NOT null like empty date fields elsewhere in Sakai. Instead, it inherits the Due date/late submission date from the overall assessment. See for more detailed description of UI/UX issues.
Wilma Hodges December 4, 2017 at 10:49 AM
Showing selections and/or text which are not applicable is confusing to end users. For example, the "Late submissions accepted?" section doesn't seem applicable when there is no end date. Also, if "No not after due date" is selected, the text below the Yes option "Students get one chance to submit after due date if they haven't already submitted" still appears. From a UI perspective, it would be better hide items that don't apply unless selections are made to make the item relevant.
Shawn Foster December 4, 2017 at 10:42 AM
What is the "retract date"? We don't see it in the UI.
Details
Assignee
Core TeamCore TeamReporter
Sean OhlingerSean OhlingerComponents
Priority
Major
Details
Details
Assignee
Reporter
Components
Priority
Major
Exception's Retract setting not 100% transparent - Uses "Yes, until" setting when not set.
If the “yes, until” is NOT set in the main assessment settings
-The retract date in the exceptions may be used or not without any interaction
If the “yes, until" is set in the main assessment settings
-The exception’s retract date is blank, it will use the “yes, until” setting
-The exception’s retract date is set, it will the exception’s retract setting
--Unsure what the desired result of the exception is but I am going under the assumption that an exception should override all assessment settings for the main assessment.