Changing visibility status must trigger a regrade
This ticket is a placeholder to address the questions posed in EDUCATOR-5523.
Should the following actions trigger a course regrade?
Changing a graded subsection to "hide entire subsection"
Changing a graded subsection to "visible to staff only"
Changing a graded subsection to "ungraded"
Currently, none of the above changes will trigger a regrade, and I assume because we didn't think that these changes would be made in a live course, or to a subsection that many learners have already received a grade for.
The main thing that the ticket points out is that doing these actions causes a disconnect between the learner's progress page and the grade report. The progress page actively filters out hidden and ungraded subsections. The grade report just grabs all persistent grading data and slaps it into a CSV.
Would we want to consider making the grade report smarter? No, the grade report should be entirely honest and report the actual grading state.
Rather than a regrade on any of those actions, should we just regrade on grade report generation?
All of these events should trigger a regrade.
All three Both events must trigger a regrade
Validate that subsections with grades are not part of of calculations or reports if hidden.
(Edit: Changing the assignment type of a subsection already fires a GRADE_POLICY_CHANGED signal, and so will be resolved by )
Steps to Reproduce
Reason for Variance
User Impact Summary
Those three actions should trigger a regrade, and these changes should reflect in both the grade report and a learner’s progress page.
There’s a separate question Ben P raised of are there types of ungraded assignment that we should be reflecting in both places, but that’s a larger discovery that would result in possibly a different solution to account for those use cases.
please chat with Ben P on use cases and best practices to help decide on feature behavior