Redesign assignment logic for feedback history and participants page
Description / Overview
In the current stage, no assignments will be created if a tutor/reviewer works on feedback within the feedback history or the participants' page. This leads to some weird code on the frontend side, like short-polling feedback on the SubscriptionWorkPage
component. This behavior is rather unintuitive, as a tutor can edit his feedback in the history while another one verifies it. We should be more strict with the assignment logic and actually create assignments in any place a tutor/reviewer can edit feedback. Simply enforcing this restriction would lead to less confusion on the user side as well as less ugly code on our side.
The code changes required to do this are rather large, as we should also incorporate some mechanisms that let the user know whether the feedback is currently editable or not. For both the feedback history and the participants' page.
Feature checklist
-
Enforce assignment creation by the backend -
Remove short-polling of feedback from the relevant components in the frontend -
Implement visual cues that show the corrector that feedback is currently being edited