nus-se-script
commented
5 months ago Team's Response
We understand that it might be restrictive, but given our target audience being TAs, it is highly unlikely for the tags to constantly change or need to be updated. The tags are usually updated once at the beginning of the semester.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: It is still possible that students can change tutorial classes and have updated particulars that TAs want to add. Even though the occurrence might not be common, when it does happen it becomes quite inconvenient for the TA. Additionally, some TAs might not want to restrict use of tags to the use cases mentioned in the UG, hence the tag feature is able to give the freedom for TAs to use the tags as they might see fit like allocating question for each student to present on and track that for instance. Tags not being cumulative restricts TAs freedom in using tags making the feature which could be one of the highlights of the product not as useful as it otherwise could be.
The current expected and actual behaviour does not allow individual tags to be added and removed. Hence it inconveniences the user when they want to edit the tags of a student to add more tags when the student already has many by forcing them to add existing ones again.