Open thewongdylan opened 5 months ago
Thank you for raising this. This behaviour is intended to give flexibility to the user, which aligns with module expectation, and would not cause inconvenience for the user in most cases. However, we believe the issue here is in the use of our word "future" in the user guide (shown in the screenshot provided), which might have given off the impression that we validate the appointment date. Therefore, we have decided to change the bug type to documentation, but will still accept this as a bug.
Team chose [type.DocumentationBug
]
Originally [type.FunctionalityBug
]
Reason for disagreement: [replace this with your explanation]
Description Appointment dates added under
d/DATE_OF_BIRTH
using theaddv
andeditv
commands accept dates before today's date, despite the UG stating that appointments are supposed to be records of a patient's future scheduled appointments at the clinic, implying that appointments must be in the future while visits must be in the pastSteps to reproduce
edit 1 o/18/04/2023
Expected behaviour The app should reject the input appointment date as it is before today's date
Actual behaviour The app accepts and saves the input date despite it being before today's date.
Reason for severity Affects usage, since there is now overlap between visits and appointments that is not checked by the app