Open Shauryan123 opened 3 months ago
Thank you for your suggestion. We agree that phone numbers and emails of courseMates should be unique in most cases, thus duplicate detection in phone numbers and emails will be useful for careless users.
However, since these types of user mistakes are uncommon (typos are unlikely to cause the email / phone number to collide with another courseMate), we're downgrading the severity of the bug to "Low". This also requires extra effort for our team to implement and considering this is not a high priority task, we will mark this bug as not in scope.
Team chose [response.NotInScope
]
Reason for disagreement: I disagree with the team's decision to mark this issue as "Not in Scope." The ability to uniquely identify a contact by email and phone number is a fundamental aspect of any contact management system. Allowing multiple contacts with identical emails and phone numbers, but different names, can lead to significant confusion and data integrity issues. This is not a rare edge case but a basic functionality that impacts the core operation of the application. The course website specifies that managing duplicate contacts effectively is essential and should be treated as a feature flaw when not handled correctly. Therefore, it is within scope to expect the application to enforce uniqueness in contact identifiers to prevent user errors and enhance data management practices.
Contacts with different names but same email and phone number are allowed in the app which does not make sense because an email and a phone number can uniquely identify a person.
Steps to reproduce:
command to enter: add John Doe -e johndoe@example.com -p 87654321 -t johndoe -s Leadership -s C++
add John Doe123 -e johndoe@example.com -p 87654321 -t johndoe -s Leadership -s C++