wallacexuhanxiao / pe

0 stars 0 forks source link

The app allows duplicated contact number without restriction #5

Open wallacexuhanxiao opened 5 months ago

wallacexuhanxiao commented 5 months ago

Different people can shares the same contact number image.png If there are only 3 or 5 ppl shares the same contact number I think it is reasonable as they are a family. However, I don’t see the limit on how many people can share the same contact number.

Maybe it is not reasonable for everyone shares the same phone number. If everyone use the same number then why do we still need this? I think this is a design flaw which potentially make the feature useless.

This would also lead to some inconvenience for users. Imagine that you want to recall some information of supplier, but you only remember his contact number, then you check the app and find 5 supplier with same phone number. You have no idea which one is your target supplier . Maybe it is better to add constraint on the uniqueness of contact number.

soc-pe-bot commented 4 months ago

Team's Response

Hi! This is a interesting point raised. However, our team feels that implementing a restriction on the number of people who can share the same phone number is not feasible. It is hard to determine what the size of the limit, since there can be so many variations.

Tester’s concern: “If everyone use the same number then why do we still need this? I think this is a design flaw which potentially make the feature useless.”

Tester’s concern: “This would also lead to some inconvenience for users. Imagine that you want to recall some information of supplier, but you only remember his contact number, then you check the app and find 5 supplier with same phone number. You have no idea which one is your target supplier “

For eg, user inputsfind p/12345678 and 5 suppliers were listed. User can stack another find command to narrow down his/her search results.

In conclusion, the tester’s concerns are based on the assumptions that the phone numbers in the list are incorrect, which is based on the input of the user, and not a bug on our app.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: [replace this with your explanation]