This issue seems to be due to how "latest assignment" is dealt. It is updated when a new assignment is added, instead of the assignment being graded. However, this is misleading and can be unhelpful when grading (cannot see changes reflected. Also, intuitively, it makes more sense to reflect the latest grade, because latest assignment will just reflect the latest assignment added for everyone anyway)
To reproduce this, simply add multiple assignments using add_asgn and only specify the name and marks. Then, grade and ungrade an older assignment for a student
This is actually intended behaviour, as it refers to latest created assignment, not latest graded assignment.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
[ ] I disagree
Reason for disagreement: [replace this with your explanation]
## :question: Issue type
Team chose [`type.DocumentationBug`]
Originally [`type.FeatureFlaw`]
- [x] I disagree
**Reason for disagreement:** Feature flaw, as this deals with the underlying ordering of assignments
## :question: Issue severity
Team chose [`severity.Low`]
Originally [`severity.Medium`]
- [ ] I disagree
**Reason for disagreement:** [replace this with your explanation]
This issue seems to be due to how "latest assignment" is dealt. It is updated when a new assignment is added, instead of the assignment being graded. However, this is misleading and can be unhelpful when grading (cannot see changes reflected. Also, intuitively, it makes more sense to reflect the latest grade, because latest assignment will just reflect the latest assignment added for everyone anyway)
To reproduce this, simply add multiple assignments using add_asgn and only specify the name and marks. Then, grade and ungrade an older assignment for a student