Handling case-sensitive for application status

[songgthu]

Application status must follow strictly the values ("yet to apply" , "in Progress", etc.) are not allowed.

[nus-pe-bot]

Team's Response

Thank you so much for the report, but we are going to classify it as NotInScope.

Here is the reason why - we have to draw the line SOMEWHERE in terms of what is considered as an acceptable variation of the Enum or not. If we consider 'accepted' as a valid input without the capitalisation, should we go about considering 'accept' as a valid input too? After all, they pretty much mean the same thing. The point is that we can NEVER draw the line at anywhere without facing some sort of opposition, so the dev team just decided that we want to draw the line at perfect, case-sensitive match. This is reflected explicitly in the UG as screenshotted below.

Even if a perfect, case-sensitive match is not the theoretical BEST design choice, we believe that it still does not warrant as a functionality bug, because the expected behavior follows what is set out in the user guide. If enough users such as yourself believe that we should make the input case-insensitive, we will implement the changes in future cycles. Hence, we will classify this 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]

---