Add field to capture phone numbers for users

There is a way to specify user’s phone number on creation/update user page. Also, a user can provide a phone number on the profile page.

@Sebastian Brudziński @Nuran Idris Does this feature already exist in Malawi? This was part of 3.3 release. If so, please mark as dead.

A few comments on this ticket:

• Suggest adding a screenshot with an arrow on it to show where the new field should go in the UI.

• Please add Acceptance Criteria, EG:

  • Suggested details would include: this field is optional, so saving a user with a blank phone number should be allowed, and saving a user with a US or a Malawi Airtel or a France/international phone number should also be allowed.

  • Need to identify any validation on phone number field.

  • Since our UI Style Guide does not have any Phone Number fields yet in OpenLMIS, we need to add a Phone Number field to the UI Style Guide. Need to decide what validation it uses. In terms of HTML markup, do we try to use the new-ish <input type="tel"> input type?

  • Since this is a new field, need to specify a migration for previous OpenLMIS systems (I believe the database migration should create the new field as blank for all existing users).

• Please add some bullets about how to test this in happy path and failure scenarios.

  • EG, test in both supported browsers.

  • Test migrating a user record (from a version of OpenLMIS without a phone number field) and then adding a phone number to a pre-existing migrated user record.

  • Test with real phone numbers from US, Malawi, and France.

  • Test erasing a phone number and saving the user record.

  • Test changing a phone number from one value to another and saving the user record.

  • Test putting an invalid entry into the web form or into the API, and what error should the API throw? What error should the end-user see?

@Ben Leibert I think you would be a good person to try to flesh out this request.

If some of these bullet points are instead items we want to leave up to the implementing developers (at SolDevelo), that is fine, but we should at least have a prompt to specify that in the ticket. The developers would fill in the rest of these details with their recommendations. They can reach out to the core team for review/feedback at any time.

After the Product Committee meeting 19 Dec 2017, Mary Jo pointed out that she believes this feature is globally-applicable and would be a welcome addition into the core product. She left the door open for further Product Committee feedback, and I haven't seen any more.