See command input not intuitive as it does not match UI

[seantham21]

Steps to reproduce: 'see d/20-11-2024'

Expected: Since the UI shows dates in the format yyyy-MM-dd, I would expect the input command to follow the same format for ease of use.

Actual: Input format is dd-MM-yyyy.

Screenshots:

[nus-pe-script]

Team's Response

The issue seems to be that the date format used for see command and the date format being shown on the schedule UI is inconsistent, thus I would argue that this is purely a cosmetic issue. The format of the see command is given in the user guide and also properly enforced, whereas the UI does also show the dates correctly so this issue should not have any impact on the users other than for purely cosmetic purposes.

I do agree that we did not consider this point and that having the date format for both to be consistent would be more appropriate for the users and should be addressed in future iterations. Since it does not affect the performance of the application for users, who can refer to the user guide, this seems to be an enhacement/suggestion for future iteration instead of an issue, thus we will be deeming it as NotInScope.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [ ] I disagree

Reason for disagreement: [replace this with your explanation]

---

## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** While I think it is indeed somewhat of a cosmetic issue, I personally felt that this issue is not simply cosmetic as it actually might affect the user's experience if they constantly refer to the schedule for the date's format when typing a command, especially if the terminal's response is also not clear as to whether it is MM-DD-yyyy or DD-MM-yyyy. This would mean the user might get many wrong entries during his/her time of use or will have to check back with the user guide every time they utilise the application. 

---