BETA Classic quizzes get "everyone else" field added to due date section when assigning specific students using new "assign to" UI

Canvas

This behavior has been resolved and deployed to the production environment as of 7/31/24.

Description

New Assign To feature:

.

That feature is adding a new “Assign To” filed under the Assignments/Quizzes/Discussions Index page. Users are able to access the appropriate index page and then select the menu option for the assignment item and “Assign To” is an option.

  • If you use this new pathway/method to assign a Classic quiz to remove the default 'everyone' and instead assign to a specific student or set of students (several individuals, sections, groups, etc.) It will also automatically add an additional “Everyone Else” Assign To field.

    • Furthermore, that “everyone else” field will not be visible from the Assign To menu in that same new ui (quiz Index page), but you can see it if you access the Assign To menu directly from the Classic Quiz’s edit options or the Assign To button that is added to the top bar menu between the Preview and Edit buttons when viewing the quiz.

Expected Behavior

All the “Assign To” methods should behave the same . You should also be able to see all the “Assign To” fields from all the pathways.

Workaround

Don't use the Assign To on the Index page to custom assign classic quizzes

Steps to Reproduce

  1. In BETA have a course with students and a classic quiz that is currently assigned to Everyone.

  2. On the Quiz index page, use the radial button menu option icon for the classic quiz to select ‘ Assign To’

  3. Remove ‘everyone’ and assign the quiz to an individual student. Save.

  4. Access the Quiz and note that the quiz is assigned to both the student and ‘everyone else’

  5. Check the “Assign To” fields though edit and the top bar of the quiz and note that you can see the ‘everyone else’ field.

  6. Go back to the Quiz index and access the Assign To from the menu there and note that that the ‘everyone else’ field is not visible.

Additional Info

LX-1891


Known issues indicate notable behaviors that have been escalated to the Canvas engineering team. Known issues are not a guarantee for an immediate resolution. This document is for informational purposes only and does not replace the Support process. If you are encountering the behavior outlined in this document, please ensure you have submitted a Support case (per your institution's escalation process) so Canvas Support can adequately gauge the overall customer impact and prioritize appropriately.

Labels (1)