Task name duplication not being checked properly - should be case insensitive

[Devanshshah1309]

Expected

Two tasks with the same name - irrespective of their casing should be considered the same task (or at least a warning should be given to the user)

Actual

The name equality is case-sensitive to Grade Mission 1 is considered different from grade mission 1 - which might lead to "duplicate" tasks (based on the problem domina) in the same list

[soc-pe-bot]

Team's Response

this behaviour of the app does not violate anything in the user guide, so it is not a functionality bug. moreover, our team does not believe task names should be case in-sensitive.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [x] I disagree

Reason for disagreement: Since you did not provide any justification as to why your team believes that task names matching should be case-sensitive, it is not convincing.

In the real world, "Grade Mission 1" and "grade mission 1" are likely the same task. Your application does not take that into account.

Also, unfortunately, the module website does clearly state that this an example of a valid feature flaw.

Bugs related to duplicate detection: Duplicate detection (e.g., detecting if two persons in the address book are the same) is not trivial; often, detecting only the exact string/value matches is not enough. For example, John Doe and john doe are likely to be the same person. Similarly, extra white space (e.g., the user typed an extra space between the two names) is unlikely to mean they are two different persons. Typically, it is best if you can give a warning in such near match cases so that the user can make the final decision. If you app has a duplicate detection feature, make sure its limitations are made clear to the user so that users are not led to believe that duplicates are being detected while many potential duplicate cases go undetected. Otherwise, it can be considered a type.FeatureFlaw.

Your app does not give a warning in near match cases and so does not allow the user to make the final decision.

Your UG does not even mention anything about duplicate task name detection, which makes matters worse.

Hence, I think it is a low severity feature flaw.

---