Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

find function could be better #3

Open
pnutzz-0207 opened this issue Apr 16, 2022 · 1 comment
Open

find function could be better #3

pnutzz-0207 opened this issue Apr 16, 2022 · 1 comment

Comments

@pnutzz-0207
Copy link
Owner

pnutzz-0207 commented Apr 16, 2022

Initially, many profiles with name containing 'cel' is added.

Screenshot 2022-04-16 at 2.33.25 PM.png

When find cel is entered, only 10, 12, 13 appeared.
A normal user would expect 11 to appear as well.

Screenshot 2022-04-16 at 2.34.22 PM.png

Understand that this is the design of the feature (shown in UG), but it is not really convenient for users. Might affect user experience when there are many profiles in the app.

@nus-pe-bot
Copy link

nus-pe-bot commented Apr 19, 2022

Team's Response

Thank you for your concern. However, if we think of the other way around (which we did), allowing celtest1 to be found by using find cel might not be a good idea as well, since logically shorter strings will find more contacts and there could be a situation where:

  1. You have a contact named Li Hsien Long, Li Jingxi, Li Lu, Lily, Lia, Lincoln.
  2. You want to find Lily, by putting Li. But, everyone stated on 1 will be listed.
    Hence, having the suggested feature will cause problem in another scenario other than what you have stated.

Moreover, even if this is a feature flaw, we certainly thing it is not a severity.Medium bug, as 1. It is not UniGenda's main feature, and 2. This issue could happen only in rare occasions, and 3. The argument above.

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

  • I disagree

Reason for disagreement: Responding to the scenario in the team's response:
If a user wants to find Lily, he/she will choose to type in Lily instead of just Li. If Lily is entered, then the names that contain Lily will appear, and those with just li will be eliminated. I believe this is what the user wants.
On the other hand, if a user types in li, it will usually be the case where the user remembers that there is a li in the name (but not which name exactly), or they would want to find all the names that contains Li. Therefore, I still insist saying that this feature should be changed according to the suggested way.


❓ Issue severity

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

  • I disagree

Reason for disagreement: [replace this with your explanation]


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants