[remind] Allows for duplicate reminders, on the same day and time

[GZTan23]

Description

As per title.

Expected

Duplicate error

Actual

Executes successfully

Steps to reproduce

• Execute remind n/John Doe e/Math exam d/2025-06-20 t/09:00 a few times

Screenshots

[nus-pe-bot]

[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]

Team's Response

No details provided by team.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

No error thrown when user sets a reminder for a student that does not exist in the address book

The remind command allows user to key in names that do not exist in the address book as a parameter for n/STUDENT_NAME, even thought the DG states that an error message should be displayed (Extension 2c). An error should be thrown to signal to users that no student with such a name exists in the address book, or at least an output should be displayed indicating that no such student exists. The current app behaviour in such a scenario could be confusing for users.

video:https://raw.githubusercontent.com/nus-cs2103-AY2425S2/pe/master/files/75cecd02-ce5c-4cfa-9b08-42dac3b562f2.mov

---

_{[original: nus-cs2103-AY2425S2/pe-interim#2009] [original labels: severity.Medium type.FunctionalityBug]}

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

This is in the planned enhancements, therefore not in scope

Items for the Tester to Verify

❓ 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: I would like to disagree on stating this issue as duplicate, since the "original" bug argues that the remind command allows for reminders to be set for non-existent contacts, whilst the issue I am contending is that the reminders do not have a duplicate detection validation for its dates set up.

Unless it is unable to be fixed independently (e.g. fixes one fixes the other issue), I believe that this issue should not be labelled as duplicate.

---

❓ Issue response

Team chose [response.NotInScope]

• I disagree

Reason for disagreement: [replace this with your explanation]

---

❓ Issue type

Team chose [type.FunctionalityBug]
Originally [type.FeatureFlaw]

• I disagree

Reason for disagreement: [replace this with your explanation]

---