search

NeoHW / pe

0 stars 0 forks source link

Event is not case sensitive #17

Open NeoHW opened 7 months ago

NeoHW commented 7 months ago

Screenshot 2024-04-19 at 4.54.26 PM.jpg

submit math assignment and Submit math assignment on same date same time is likey due to a typo and means the same thing, but is treated as 2 separate events.

schedule add h/submit math assignment t/2/31/2024 0930 d/Discuss project details n/Bernice Yu schedule add h/Submit math assignment t/2/31/2024 0930 d/Discuss project details n/Bernice Yu

soc-pe-bot commented 6 months ago

Team's Response

We recommend changing the severity from Medium to Low. Although it is possible for duplicate appointments to be added like this, it does not pose much inconvenience to the user. The user can simply use the schedule delete command to delete the duplicate. Moreover, we allow this functionality to allow for recurring events, for example, if you meet alex twice in one week, you can write Meet alex and meet alex (since headings are unique). Also it is quite unlikely that the user types in the same command twice and has a typo. Hence, we believe that this bug should be assigned low.

Items for the Tester to Verify

:question: Issue severity

Team chose [severity.Low] Originally [severity.Medium]

Reason for disagreement: While it may be true that duplicate appointments can be easily deleted using the schedule delete command, this overlooks the fact that users may not immediately recognize the duplication and may inadvertently overlook or forget to delete one of the duplicate appointments.

Moreover, we allow this functionality to allow for recurring events, for example, if you meet alex twice in one week, you can write Meet alex and meet alex (since headings are unique).

Allowing for the possibility of duplicate appointments due to minor typos or variations in naming conventions can lead to cluttered and confusing schedules for users, particularly if they rely heavily on the scheduling functionality of the product. Even though it may be unlikely for users to type in the same command twice with a typo, the consequences of such duplicates can still be significant, potentially leading to missed appointments or misunderstandings in scheduling.

For example, if Alex is a very good friend of mine, and I would meet him 5 times in a week: I would have to write "meet alex", "Meet alex", "MEet alex", "MEEt alex", "MEET alex". If they were to accidentally have a typo which leads to duplication, How then does one differentiate which is intended and which is a duplicate to be deleted?

This method alone of using different capitalisation to represent different events is an inherent flaw by itself.

Therefore, maintaining the severity of the bug as Medium is appropriate, as it accurately reflects the potential inconvenience and usability issues it may cause for users.