Open axmszr opened 1 year ago
Thanks for the feedback, we reject this bug on the basis that task names can be easily specified and are usually specified to differentiate them and thus this will not cause an issue for the vast majority of users. For example if we had a recurring task and wanted to differentiate them it could easily be written as "recurring task 1", "recurring task 2" and so on, alternatively the user could create a todo task for one instance of recurring task and mark/unmark it instead of creating a bunch of tasks with the same name which would be wasted labour
Team chose [response.Rejected
]
Reason for disagreement: [replace this with your explanation]
Summary:
Tasks are considered duplicates if they contain the same name, even across the different task types. What happens if a user has a recurring task?
Steps:
deadline task/abc by/14/04/2023
, and it is added successfully.deadline task/abc by/14/05/2023
, and it cannot be added.todo task/abc
, and it cannot be added.Image: