Open chuababyy opened 11 months ago
We thought this was not a FunctionalityBug because it works as expected and we did not intend to detect duplicate tasks assigned to a member. We have put this as NotInScope because we don't think that we should unnecessarily restrict users input for task names (they might want to add multiple tasks of the same name for recurring tasks, for example).
Team chose [response.NotInScope
]
Reason for disagreement: I believe that the duplicates check should be implemented in the current iteration for the following reasons.
addt 2 /task Implement solve feature
I am able to enter this command multiple times, and it will add the same task over and over again, leading to multiple duplicate entries for the same person.
Doing
addt 2 /task Implement solve feature and then addt 3 /task Implement solve feature
will also not lead to any duplication errors.
Screenshot 2023-11-17 at 4.56.17 PM