soc-pe-bot
commented
1 year ago Team's Response
Thanks for bringing that up! However after considering this feature design and also reviewing the website's description of such a functionality design ("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."), we have come to the conclusion that since we do not use client names for any legal or official purposes but only for the developer to track his or her clients for the projects and mainly, contact them as needed, disallowing certain inputs does not affect the purpose/usage of the client list. Moreover, the inconvenience cause by this are in rare instances(therefore, the change in severity level) and that too, are not hindering the central reason why a clientlist (for tracking and quick contacts) is used. Nonetheless, this is a feature that we can open up in future versions of the project though it does not fall in the scope of our current version. Kindly note that the current tag for this would be a FeatureFlaw as the constraints in Name (disallowing certain characters) are displayed and work as expected.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
:question: Issue type
Team chose [type.FeatureFlaw]
Originally [type.FunctionalityBug]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
:question: Issue severity
Team chose [severity.Low]
Originally [severity.Medium]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
Unable to add names with S/o or D/o, leadning to some inaccuracy in name storage.