nus-se-script
commented
1 day ago Team's Response
Thank you for your bug report. Our sort feature works perfectly as stated in the UG. Allowing the user to give a parameter on which direction the sort works is a valid feature enhancement but it does not mean that the existing feature does not work.
The user is also not hindered in his or her usage in anyway but the lack of this feature enhancement.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [x] I disagree
Reason for disagreement: Thank you for your response. I acknowledge that the feature works as described in the UG, which is to sort the clients by name alphabetically.
However, it is reasonable to assume that as a sort function, it is also likely that the user will have to sort by descending order to search for specific clients. As the number of clients increase, if the sort function only works in ascending order, it would mean that the user will have to scroll very far down to find clients whose names start with a letter from the second half of the alphabet (N-Z).
For most applications or website (e.g. excel), if there is a sorting function, it is highly likely that the sort function allows for bidirectional sorting as it helps to deal with large datasets. In the case for this application, it is very possible for the user to have many client's contact stored.
Hence, this could pose as a potential inconvenience for users and is less useful for users who would like to be able to sort in both directions.
Screenshot 2024-11-19 at 4.56.41 PM
The sort command currently does not take in any parameter to determine the sorting order. This can prevent users from benefiting from this command for the case when they need to sort the client list in descending order instead. Perhaps this could have been included in the planned enhancement section