Open joshruien opened 4 years ago
We accept this as a very low severity bug as it does not affect usage and functionality. Although the error message is different, it does still tell the user what is the correct index to input. Hence, technically the error message displayed is not wrong.
Team chose [severity.VeryLow
]
Originally [severity.Low
]
Reason for disagreement: It still affects usage because users are not prompted that the index is invalid but that it was an invalid command. This can cause minor inconvenience as the user has to figure out by himself or herself what was wrong with the command and why it was invalid instead of getting the correct error message that the problem lies with the index.
Both are invalid appointment indexes however the error message does not display if the index is less than or equal to 0.