soc-se-bot
commented
1 year ago Team's Response
No details provided by team.
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Invalid error message when adding event
Instructions were followed to put in the dates in the required format, however the error message still states that the dates were given in an invalid format.
[original: nus-cs2103-AY2223S2/pe-interim#46] [original labels: severity.Medium type.FeatureFlaw]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
We think that the severity of this bug should be reduced. This is because the chance of a user keying in a date that does not even exist is low, given that this application is meant to record dates of already scheduled meetings and interviews.
This bug is only seen if the date format is wrong or the date does not exist (like 30th February) at all, so for dates that do not exist they technically are not formatted correctly, thus making the error message relevant.
As you can see for proper dates a more descriptive error is thrown.
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)
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
## :question: Issue type Team chose [`type.FeatureFlaw`] Originally [`type.FunctionalityBug`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
[Expected] When user enters invalid date (e.g. 31/02/2023), error message should warn users that date is invalid/does not exist.
[Actual] Error message claims that date is not in the right format, which is not entirely accurate (date entered does follow the right format).