nus-pe-bot
commented
2 years ago Team's Response
We clearly stated in our user guide all of the accepted command formats. For example for add client, the format is
Users are expected to follow the user guide. Since the command word in the command format is already shown as case insensitive, there should not be any doubts.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: Specifying the command name in lower-case letters in the command format doesn't automatically imply that it is case sensitive in nature.
The purpose of the user guide is to assist users in using a particular product and mention all the command constraints in an explicit manner, so I would expect the team to have clearly mentioned in the 'Notes about command format' section that all command names are case sensitive. This simple action would have avoided confusion regarding the case sensitivity of command names.
Therefore, it is classified as a bug with low severity.
:question: Issue severity
Team chose [severity.VeryLow]
Originally [severity.Low]
- [x] I disagree
Reason for disagreement: I think the team is not clear with the distinction between low and very low severity bugs. These are the definitions of the low and very low bug severities according to the website:
-
severity.VeryLow : A flaw that is purely cosmetic and does not affect usage e.g., a typo/spacing/layout/color/font issues in the docs or the UI that doesn't affect usage. Only cosmetic problems should have this label.
-
severity.Low : A flaw that is unlikely to affect normal operations of the product. Appears only in very rare situations and causes a minor inconvenience only.
This bug is clearly not purely cosmetic in nature. It affects the usage since users are unclear about the case sensitivity of the command names. Moreover, this bug is unlikely to affect normal operations of the product and will only cause a minor inconvenience in rare scenarios.
Therefore, it should be classified as a low severity bug.
UG doesn't talk about whether the command names itself are case sensitive or not. The error message in the app itself deems it as an unknown command, so there could have been better clarification regarding this in the UG