Using incorrect prefix in policy leads to incorrect data in policy name

[Cedricaca]

i understand this is most likely just a feature of an optional field and allowing non alphanumeric characters into po/, but given a insurance company might want to avoid errors like this might be best to classify this as a feature flaw

[soc-pe-bot]

Team's Response

This can be considered a future enhancement. But since the app works fine if you use the correct prefixes and the error is easily spotted and fixed with our edit command, we label it as NotInScope.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [ ] I disagree

Reason for disagreement: [replace this with your explanation]

---