Open Alteqa opened 5 months ago
Thank you for pointing this out, we do agree that the error message provided does not let users know the right command format, which is a lapse on our part.
However, we feel that the severity of this bug should be a Low
instead of a Medium
. This is because new users are likely to be testing the app alongside the UG, where they can easily access information on the correct format of the Switch
command. Furthermore, we feel that it is rather intuitive for users to include another parameter after switch since switch suggests that there needs a name to be switched to. Hence, we find that this issue is be a common occurence amongst users, and even if it does happen users can easily check out section on the Switch command in the UG. However, we do acknowledge the issue and will likely make the error message clearer in future iterations.
In terms of type of bug, we also find that this is more of a feature flaw rather than a functionality bug. This is because the switch command is able to execute properly and throw error messages where the command is invalid, working as expected. The issue rather is that the error message is unclear which may confuse users. Hence we have identified this as a feature flaw instead.
Team chose [response.NotInScope
]
Reason for disagreement: This is a genuine bug that is in the scope of a regular user using the software. If the error message provided in the output terminal is incorrect, the user may try to enter using the format provided below which will not give them the functionality they originally desired. This defeats the entire purpose of the output message and is fixing it is definitely related to the current release of v1.4 where the switch command is advertised as a feature. As such, this is a valid and significant bug in the scope of the current iteration.
Instead of suggesting texts for switch fields, it gives an invalid command output for edit: