Open YuZizhen opened 5 months ago
Both bugs spawn from the same process of checking duplicate persons. if the defective person checking was fixed, both problems would be fixed.
[The team marked this bug as a duplicate of the following bug]
Same name mistaken as separate entity / people
John Doe and John doe is the same person but it record as different people
[original: nus-cs2103-AY2324S2/pe-interim#787] [original labels: type.FunctionalityBug severity.High]
[This is the team's response to the above 'original' bug]
This issue causes occasional inconvenience to some users, but they can continue to use the product by deleting the duplicated contact. this would not render the app unusable for the end users therefore it is not suited to be high severity as stated on the course website
Items for the Tester to Verify
:question: Issue duplicate status
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
Reason for disagreement: [replace this with your explanation]
Maybe for a financial advisor, name might not be the best check for duplicated person. It is highly likely to have multiple person with the same name. Thus, the user cannot put all of them inside FApro