search

triciiaaa / pe

0 stars 0 forks source link

Find feature uses the field names rather than prefixes #7

Open triciiaaa opened 4 months ago

triciiaaa commented 4 months ago

Description

When adding and editing fields, we use the prefixes n/, e/ etc, but for the find feature, instead of searching for contacts via the prefixes, users have to type the field for e.g. name instead of n which affects the efficiency of the user.

Screenshots

image.png

nus-pe-script commented 4 months ago

Team's Response

Find is supposed to be consistent with sort, and we also think that there is no major difference in efficiency between name and n/

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: Thanks for the response! While I don't agree that this bug should be rejected, I think the team can consider working on this for future iterations instead. I don't really understand the need to adhere the find command with sort command, since the other features in the application (e.g. add command and edit command) use prefixes instead (as iterated in my issue description). This may confuse users and hinder them since they would have to remember that prefixes are used for add and edit, while full field names are used for find and sort, I believe there should be some sort of consistency throughout the application, and thus, selecting response.NotInScope would be more suitable for this bug.