Cannot add Event with the same name even when location/time is different

[JunLongling]

Example: Event that already exists in VolunSync /e new n/Blood Donation Drive l/Red Cross Center d/2024-02-14 s/08:30 e/16:00 des/Organizing a blood donation drive

I cannot add /e new n/Blood Donation Drive l/Blue Cross Center d/2024-02-14 s/09:30 e/16:00 des/Organizing a blood donation drive

As blood donation is a common event, there may be multiple blood donation event happening in the same day but different venue or time, the user should be able to add them

[nus-pe-script]

Team's Response

No details provided by team.

The 'Original' Bug

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

Typo in UG

Note in UG for add event: supposed to be existing event and not exisiting volunteer

Suggestion/ Why it is problematic: Users may not know that it is supposed to be existing volunteer and not event and may run into errors when trying to input duplicate events.

Screenshot:

---

_{[original: nus-cs2103-AY2425S1/pe-interim#2979] [original labels: severity.Medium type.DocumentationBug]}

Their Response to the 'Original' Bug

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

Thank you for raising the issue, we do recognize that it is a typo on our part, but we believe that it does not warrant a medium severity. Instead it should be of a low severity.

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)

• [x] I disagree

Reason for disagreement: Thank you for reviewing my bug report. However, I believe it has been incorrectly marked as a duplicate. My issue highlights a feature flaw where events with the same name but different locations or times cannot be added, which impacts real-world scenarios such as organizing recurring events like "Blood Donation Drive" across multiple venues. This is distinct from the original bug, which concerns a typo in the documentation about volunteers and does not address the feature limitation I reported.

---

## :question: Issue type Team chose [`type.DocumentationBug`] Originally [`type.FeatureFlaw`] - [x] I disagree **Reason for disagreement:** Its a feature flaw, not a documentation bug

---

## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** The inability to add events with identical names but different locations or times contradicts VolunSync's core value proposition of streamlining event management for nonprofits. As the product scope highlights, the target users need an efficient way to manage extensive event databases, and the application is designed to facilitate accurate records and smooth coordination.  For instance, event directors often plan multiple sessions of the same event, such as "Blood Donation Drive," across different venues and times. However, the system currently prevents storing more than one event with the same name, even if the location and time differ. This forces users to rename events, which undermines the app's usability by adding unnecessary complexity and increasing the risk of errors in event planning. This feature flaw directly affects the "Create events" functionality, which is a high-priority user story outlined in the app's intended capabilities.  Renaming events is not a valid solution because the current behavior is not aligned with the product's intended functionality as described in its product scope. The inability to store multiple events with the same name but different locations or times is a clear functional oversight. This limitation is not a matter of NotInscope but a usability feature flaw that prevents users from performing basic event management tasks as expected.  Given that many events, such as "Blood Donation Drives," are recurring by nature, this issue will arise repeatedly for users attempting to manage such events. The recurring nature of this problem amplifies its impact, causing ongoing and important inconveniences in planning and organizing events. This directly meets the definition of medium severity, as it disrupts essential workflows for a significant portion of users. 

---