Description

Given this product is targeted at Singapore, it is imperative that we understand that Singapore is a multiracial country with a significant indian population and certainly Indian beneficiaries will be involved. The term "d/o" daughter of is definitely not uncommon in indians. However, I am unable to add in an indian name as such . Ideally date should be phased as a dt/ instead of d/ to avoid this issue as it is not inclusive for indian beneficiaries at this point of time.

In fact, names with s/o seems to be able to be added, so why is "d/o" explicitly not considered?

[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]

Team's Response

Fair enough, with regards to limitation of parsing. This is already mentioned in the Known Issues of the User Guide (screenshot point 4), and a workaround has been proposed that will work. As this is mentioned and a solution for the users has been proposed, users should know to avoid doing this. This lowers the severity of the issue. It is also worth mentioning that d/o means (daughter of) similarly a/p and a/l means daughter of and son of in Malay. Omitting these abbreviations from names shouldn't be too impactful even in the worst case scenario, but we provided a work around anyways. Hence, this is low severity.

Items for the Tester to Verify

:question: Issue severity

Team chose [severity.Low] Originally [severity.Medium]

[ ] I disagree

Reason for disagreement: [replace this with your reason]

taggyhan / pe

Names do not allow indian names which might hinder users with d/o in their legal names. (e.g. "d/o" is not uncommon in Singaporean Indian names) #5

Description

Steps to reproduce

Expected behaviour

Actual behaviour

Team's Response

Items for the Tester to Verify

:question: Issue severity