Open NeoHW opened 6 months ago
Good catch! However, it is quite rare that the user inputs an incorrect date of a leap year and does not catch the mistake that occurs. Moreover, if they were to actually write this date they likely intended to write 2/29/2024 and not 2/31/2024. As such the inconvenience is not so great, thus, we would like to reduce the severity to Low and change the bug to Functionality bug.
Team chose [type.FunctionalityBug
]
Originally [type.FeatureFlaw
]
Reason for disagreement:
As seen in the screenshot from CS2103 Website
schedule add h/Meeting with Client3 t/2/31/2024 0930 d/Discuss project details n/John Doe
Date given is 2/31/2024, but user is not warned of anything but instead a wrong data of 2/29/2024 is added in instead