Phone field invalid when editing a contact with a valid phone number

[latin-panda]

Describe the bug
Phone field is highlighted as invalid when editing a contact with a valid phone number, because it already exists and can't save unless the phone field gets a new value. It should not highlight the field because the contact is the phone number owner.

To Reproduce
Steps to reproduce the behaviour:

1. Create a new contact with a unique valid phone number.
2. Save contact.
3. Click edit contact and modify another field that is not phone number.
4. Click save and observe how the phone field is hight lighted as wrong.

Expected behavior
Should not high light the field as wrong if the phone is correct and the contact is the only one assigned to that phone.

Screenshots

Environment

• Instance: local (master) and https://gamma.dev.medicmobile.org/
• Browser: Chrome
• Client platform: MacOS
• App: webapp
• Version: 3.11 - 3.12

[dianabarsan]

Ready for AT on 7261-edit-contacts-with-phones.

[meghna-khemka]

Tested above mentioned issue and above issue seems to be working fine but I observed unconsistent behaviour while creating a person with a Phone Number. I do face above mentioned error while creating a new person (Not always but sometime).- Supporting doc attached- (last one -Issue.while.creating.Person.mov)

Both.num.mov

Alternate.Phone.number.mov

Phone.Number.issue.mov

Issue.while.creating.Person.mov

[dianabarsan]

@meghna-khemka
The phone numbers are both validated, and also checked against other contacts - as two contacts should not have the same phone number. This was what caused the issue in the first place.
In your last video, can you pls make sure you don't have another contact that already uses that phone number?

If you don't, this seems to be another issue. Can you please share the logs from the browser console? Thanks.

[meghna-khemka]

Thanks @dianabarsan
Yeah,It's working fine when we use different phone number's ,may be I was expecting different error message when 2 contact's have same Phone number but looks to be fine if we are displaying same error message.

Happy to pass as mentioned issue is working fine :)

[dianabarsan]

Thanks @meghna-khemka for the quick AT and feedback!

Merged to master.