Overzealous name autoformatting

[trpmy]

The app supports this useful autoformatting for names:

However, some names where children share their father's name and take on an ordinal in their name, such as John William II, is forcefully and wrongly formatted against the user's will as John William Ii.

Worse yet: There is NO WORKAROUND. Not even editing would allow me to change to the ordinal that I want.

I put this at medium because this is only an occasional inconvenience to some particular users only, which deserves severity medium.

[nus-pe-script]

Team's Response

We lower the severity to VeryLow, as it is purely cosmetic. Our intention to include auto-formatting is to beautify the product.

We also specifically mentioned in our planned enhancements, that we will be supporting more comprehensive language support in the future, including ordinals, so we reject the bug.

It would require too much effort to check for all types of ordinals currently, when inputting a name.

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

• I disagree

Reason for disagreement: >We also specifically mentioned in our planned enhancements, that we will be supporting more comprehensive language support in the future, including ordinals, so we reject the bug.

The word "ordinals" appear nowhere in any planned enhancement. Furthermore, the planned enhancement, verbatim, supports "names with special characters and non-English names". John William II is very much an English name, and the II is very much alphanumeric. They're literally just two capital i's. This planned enhancement is irrelevant to this issue. It's only to guard against criticisms of special characters, which is not my point.

It would require too much effort to check for all types of ordinals currently, when inputting a name.

I don't think "requiring too much effort" is a valid reason to reject a bug. I would've accepted NotInScope, and this reason would've been acceptable, but sadly the team decided to reject outright. I really wished they had just said NotInScope, but this response forces my hand to dispute their decision.

---

❓ Issue severity

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

• I disagree

Reason for disagreement: > We lower the severity to VeryLow, as it is purely cosmetic. Our intention to include auto-formatting is to beautify the product.

This beautification leads to, what I believe, a Medium-severity bug. It's nice that the team also told me their intention, but ultimately irrelevant.

Please consult my original bug report. A cosmetic issue would've been with how the UI displays names, but this is very much not cosmetic. It forcefully autoformats names like into John William Ii (which also looks like the lowercase chinese name li, adding further to confusion/annoyance), and there is no workaround, not even editing . It's very much not cosmetic: this is literally the data the user is trying to put into the app, and the app is forcefully modifying the data in a way that is against the user's will and for which there is no workaround. This data is then recorded and operated on (for example, the name John William II is recorded as John William Ii. There is literally no existence of "John William II", even in the backend).

For an app that records contact details, this forceful approach is a flaw in the feature, more than "purely cosmetic".

I put this at medium because this is only an occasional inconvenience to some particular users only, which deserves severity medium.

---