Team's Response

No details provided by team.

The 'Original' Bug

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

Invalid date is not addressed

29-02-2021 is invalid but the app accepts it without showing error. Mistakenly adding wrong date is quite common especially in the case of February; user needs to be notified.

---

_{[original: nus-cs2113-AY2324S1/pe-interim#87] [original labels: type.FunctionalityBug severity.Medium]}

Their Response to the 'Original' Bug

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

Thank you, the team appreciates the reported bug. However, the program has multiple levels of fail-safes to allow the user to ensure that his inputted parameters are valid in accordance with what he intended to track. This is evident as the program shows a printout of the transaction the user has added.

This should be sufficient for the user to know that the input processed is not the same as his intended input.

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: [replace this with your explanation]

❓ Issue response

Team chose [response.NotInScope]

• I disagree

Reason for disagreement: It is definitely InScope as we should be handling invalid dates and returning the respective error message to the user and not accept the invalid date.

❓ Issue severity

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

• I disagree

Reason for disagreement: > severity.Medium : A flaw that causes occasional inconvenience to some users but they can continue to use the product.

This issue does not only cause minor inconvenience as the user may have accidentally inputted February instead of march and now the system accepted the invalid date, causing functionality issues down the road.

from pe.