You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sort commands are not intended to be able to sort by optional fields as shown in the note section. It's our mistake that we include the example in the UG, however, it's only a minor inconvenience, thus does not affect any other operations. Thus, this should be low severity.
Items for the Tester to Verify
❓ Issue severity
Team chose [severity.Low]
Originally [severity.Medium]
I disagree
Reason for disagreement: According to the CS2103T website, the bug actually affects most users and causes major problems for users as this command is not executable at all. However, since the sort command might not be commonly used as compared to add and edit commands, I believe this flaw causes occasional inconvenience to some users but they can continue to use the product. I don't think this happens in rare situations as this command is explicitly stated in your UG. Hence the severity should be medium.
I tried to use the sample "sortC by/alg o/a" command stated in the UG, however, it turned out that the app did not support this operation.
The text was updated successfully, but these errors were encountered: