The documented feature 'appointment' is not present in the actual app

[huekoh]

[Context] Under the features section of the user guide, there is a distinguishment made between the appointment field and the visit field. However on the application itself, only visit is available for use and appointment, which affects some commands such as list-by-date and list-until-date is not visibly available for use on the app and has no defined commands to use it either. (Refer to user guide command summary)

[Problem] This causes affected commands such as list-by-date and list-until-date to produce erroneous behaviour, list-by-date's functionality bug is recorded as an issue for reference as well.

[Commands that utilise appointment]

[soc-se-bot]

Team's Response

When you first run the application, some of the sample data has an appointment date. If there is no appointment, then it will be shown empty and it seems like this has caused a misunderstanding.

Furthermore, an appointment can be added by the edit command as shown in the user guide. Since appointment is one field, we decided to allow to make changes in appointment by edit command. On the other hand, visit is a list, so we had to implement separate commands for it.

Lastly, this bug is not related to the quality of documentation, so we can't accept it.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [ ] I disagree

Reason for disagreement: [replace this with your explanation]

---

## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.High`] - [x] I disagree **Reason for disagreement:** *Disclaimer I chose to disagree with the severity to allow myself to write a feedback, but i agree with both the dev team's severity and response* Thank you for the response, I had missed that one of the pre-populated contacts had an existing appointment to visualise that it exists on the GUI for first time users. I feel that since a lot of the commands such as `list-by-date` and `list-until-date` are dependent on appointment rather than visit, a more intuitive GUI representation would be to place emphasis on `Next Appointment` rather than `Latest Visit`. Because `Latest Visit` is visible on the GUI even if a contact does not have a latest visit, while `Next Appointment` is not visible at all unless the contact has a next appointment, it's quite confusing for a first time user, and led me to believe that the list sortings were by visits (or rather that visit and appointment were synonymous), and I wasn't even aware the appointments existed on the GUI because it is so small until i re-read the User Guide.

---