Open hsiaotingluv opened 2 years ago
This bug should be classified as Low because this is a rare occurrence, and that the user can simply add additional information in the name field to differentiate the two users.
Team chose [severity.Low
]
Originally [severity.Medium
]
Reason for disagreement: This bug can potentially causes great inconvience in many occasions. In the case if an agent does not know the full name of a client yet e.g. Amy, they cannot have multiple clients with the same name existing in the app. This can be a frequent problem especially because an agent will have to network with multiple clients at the same time, and it is common for people to share the same name.
Hence, severity remains at Medium.
Input: add n/John Doe p/98065432 e/amy@example.com a/simei st. 1
Expected: Accept as different person
Reason: there are people with exactly same name and surname, people with same name but different phone / email / address should be considered different person