Name input do not allow s/o which is a valid name. UG do not specify it restricts this constraint as well.

[yixiann]

It is acceptable to disallow certain characters in input values if there is a justification (e.g., because using those symbols in an input value makes the command harder to parse), but they can still be considered FeatureFlaw bugs if they cause inconvenience to the user. For example, disallowing s/o in a person name because / is used as a command delimiter can cause a major problem if the input is expected to match the legal name of the person.

Low severity is given as we may not need to include a full name to identify our friends. However, this prevents certain names from being entered.

[nus-pe-bot]

Team's Response

Our target users are university students, and the intended use of the app is to track debts between friends or acquaintances. It is unlikely that they would want to save their full legal name in the app, nor is there a need to. It is a possible extension in future iterations though.

Moreover, we have also recommended against using unnecessarily long inputs in our UG.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [ ] I disagree

Reason for disagreement: [replace this with your explanation]

---