Descriptions should not be case sensitive

[zacchaeuschok]

In general, the case sensitivity of something should follow the case sensitivity of the real-world entity it represents. Descriptions are usually not case-sensitive e.g., lunch and Lunch should be seen as the same description.

This may lead to duplicate descriptions in debts.

[nus-se-script]

Team's Response

The UG mentions that debt description is case sensitive and even provides recommendations on how to make use of this feature effectively and responsibly.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [x] I disagree

Reason for disagreement: While the UG does mention strategies for using case-sensitive descriptions in organising debts, it does not seem to be a very useful workaround when the alternative is simply to use a more precise description (e.g., fried chicken lunch and okonomiyaki lunch instead of lunch and Lunch).

Therefore, I categorised the case-sensitive description as a type.FeatureFlaw, because it may lead to duplicate debts being written that go undetected simply because of case differences.

---