Open jamz903 opened 11 months ago
We recognise that this is a legitimate feature flaw to warn the user on duplicate emails/phone numbers.
However, the team puts forward that this feature flaw is less critical than the existing added features, and hence response.NotInScope
.
The reasoning is as follows :
I.e. for every instance where a user enters a duplicate, incorrect phone number / email, it is about as likely that they enter an incorrect phone number / email that isn't a duplicate, and the steps to remedy this issue in the current iteration are exactly the same (edit ......
)
E.g. it does not really make a difference to the user if they entered "duplicate@duplicate.com" instead of "wrongEmail@wrongemail.com", as both are wrong and will need correcting.
Also, we downgrade the severity of the bug to severity.Low
, as it would only cause minor inconvenience if they enter the duplicated emails.
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
UG specifies that it does not allow contacts with duplicate full names to be added, but does not talk about other fields.
A contact application should have validation to check for duplicate emails, or duplicate numbers and warn the user, but the application does not check.