nus-pe-bot
commented
2 years ago Team's Response
No details provided by team.
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Edit claim case sensitive
Input: claim 9 n/heart surgery d/Description
expected: edit the heart surgery successfully
[original: nus-cs2103-AY2122S1/pe-interim#4896] [original labels: type.FunctionalityBug severity.Medium]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
This is a design choice as we cannot be sure what format the user might want to differentiate claims.
Items for the Tester to Verify
:question: Issue duplicate status
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: Can potentially cause minor or even occasional inconvenience to users in situations where the data is huge. With many claims listed, without the ability to detect case insensitive, user will have to scroll through the entire list of claims to find their specific phrasing for a claim. This causes great inconvenience and would slow down the user, making the app less effective.
Additionally, instead of using name casing to differentiate claims, should be using descriptions. A user can have multiple claims with the same name but different descriptions.
Severity lies between low and medium.
Input: claim 1 n/lost luggage
Expected: delete Lost Luggage claim
Reason: User might not remember the exact casing he uses in all claims, especially if data is huge