Open NicholasTanYY opened 4 months ago
No details provided by team.
[The team marked this bug as a duplicate of the following bug]
addtask
recognises duplicate when task does not exist
I am unable to add a task that clashes with any existing task. This may pose a problem, for example if I have an event from 11am to 3pm and I may need to run a quick errand from 11.30am to 12pm. I will not be able to add that into my timetable to track it.
[original: nus-cs2113-AY2324S2/pe-interim#2560] [original labels: type.FeatureFlaw severity.High]
[This is the team's response to the above 'original' bug]
This is what we purposely designed such that no 2 event happens concurrently.
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)
Reason for disagreement: My issue: TLDR~ The existence of the addtwdc command is questionable (or pointless). Duplicate handling should be done in the other add methods instead.
Their issue: TLDR~ The user cannot have multiple events at the same time.
Since the addtask command's objective is already to add a new task into the current user's list, it might inconvenience the user to use another command such as addtwdc to add tasks. Addtask should already check if the task is a duplicate, rendering the other command addtwdc to be not as effective.