nus-se-bot
commented
4 days ago Team's Response
It is stated in the User Guide that each tag should be one word and alphanumeric. Rejecting "groom's husband" as a tag is expected behaviour as the ' would not be allowed.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: My apologies for the confusion earlier, but I believe the purpose of tags has not been adequately explained, leading to potential user confusion. For example, while the sample data includes tags like "photographer" or "videographer," users might naturally assume they can create custom tags for specific roles, such as "groom's husband" or "main emcee." Encountering an error when attempting to assign such tags can cause frustration, as users are forced to work around the system’s restrictions instead of using meaningful and appropriate labels.
Furthermore, according to the bug triaging guidelines, it is acceptable to disallow certain characters in input values if there is a valid justification, such as avoiding issues with command parsing. However, such restrictions can still be classified as a bug if they significantly inconvenience users.
In the case of tags, restricting their flexibility without a clear justification or proper documentation falls into a similar category. This limitation causes unnecessary frustration and undermines the system's usability. Allowing special characters in tags, where feasible, would be a simple and effective solution. Alternatively, providing clear documentation that explains the purpose and constraints of tags would help set user expectations and improve the overall experience.
Tag description is not detailed, i wish to give groom's husband tag but not allowed