nus-pe-bot
commented
2 years ago Team's Response
The format of the error message is not a hard guideline to be followed. Including too much information in the title may lead to unnecessary cluttering, and can distract the user. This is a design choice we made for our product.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: The key point I was raising is that the main error message is "Invalid Tag Name" instead of "Reserved tag can only be edited by supervisor"
Since reserved tags are a fundamental feature of the application. It goes to stand that it must be handled appropriately and as clearly as possible for the users. From the way you've highlighted it in your UG, it is clear to me that these reserved tags are meant to be frequently used and important. It is quite important then that a more useful error message differentiates a reserved error from an invalid tag name.
At an immediate glance, the user will see the heading message of invalid tag name, implying that the wrong tag name was used. It should be reserved tag heading instead. This is required as error messages are listed like so
and in typical usage, people expect the additional comments to be additional, unnecessary information. The title should not be flat out wrong. However, as people will reread to make sure on their second / third attempt, I will mark this as Very-Low.