search

tigerting98 / pe

0 stars 0 forks source link

'Find' autocomplete missing all the search parameters #6

Open tigerting98 opened 3 years ago

tigerting98 commented 3 years ago

image.png

The autocomplete for find does not include any of the optional search tokens, of which at least one must be present. It would be more useful for the user if an autocomplete option had all the tokens like n/ or pd/ or autocompletes with at least one token present to allow the user to quickly complete a find command

nus-pe-bot commented 3 years ago

Team's Response

Our team intended for autocomplete command to help users to autocomplete the compulsory prefixes for each command. This is mentioned in the User Guide as well as shown below:

image.png

In addition, our team thinks that if we provide autocomplete for numerous possible ways which users can enter the prefixes (e.g. find ct/s n/, find ct/w n/, find ct/s n/ p/, etc), the autocomplete list will be very long and it would be extremely inconvenient for users to go through the long list and select the right type of command that they are looking for in the list. Hence, after much discussion, we have decided for autocomplete to simply list out the compulsory prefixes.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: While the User Guide does state that only compulsory prefixes are provided in the Autocomplete feature, since the bug category is a FeatureFlaw, having the application abide by the User Guide does not dismiss the problem. This FeatureFlaw may make it rather inconvenient for users who are just starting out in using the application who have to constantly refer to the User Guide for usable prefixes. While having all possible combinations of prefixes does indeed result in a very long list, perhaps one autocomplete command with all the prefixes may help new users get used to what prefixes are available to use in the search.

:question: Issue severity

Team chose [severity.VeryLow] Originally [severity.Low]

Reason for disagreement: Since this FeatureFlaw affects usage (slows down users who are not yet familiar with the prefixes that they can use in the find feature), I believe that it is not "purely cosmetic and does not affect usage", and should be classified with a Low severity rather than VeryLow severity.