Open ricketytoc opened 12 months ago
The reason our current system only support 1 memo per student is we believe this will keep the overall UI clean and the memos are always up-to-date. This design decision is to keep the consistency in the update principle among all attributes of a student, so users will not get confused while using our edit student command.
We have mentioned this edit policy in the Info box of the Edit Student feature in our UG:
Nonetheless, thank you for your perspective regarding this issue.
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
Description
After adding a memo to a student, when edit the student's memo it replaces the old memo.
Expected Results
New memo gets added on top of the old memo.
Actual Result Old memo gets replaced
Justification I understand that this is stated already in the UG, but I think that a tutor might want to keep track and add upon past memos about a student. I think that this reduces the usefulness of the memo feature as users will need to completely retype the old memo along with the new memo if they wanted to add upon the old memo.