An edit that causes a duplicate appointment is not caught by the system

[Shantaa]

Given a situation where an appointment already exists, attempting to an appointment to be have the same details results in the system not catching the error and not prompting the user about the situation, which may lead the user to think that the system is not responding.
Note the terminal throwing the error below.

[soc-se-bot]

Team's Response

The GUI does prohibit duplicate appointments as mentioned in the UG, so it is working as intended. The issue is that the GUI is not telling the user that this is the case. Since this is an issue related to an incomplete terminal output and does not break/crash the application, we believe that the severity of this issue can be decreased to low.

Additionally, adding this terminal output was not as important as getting the edit appointment feature to work, so our team considers this as out of scope for now.

Items for the Tester to Verify

❓ Issue response

Team chose [response.NotInScope]

• I disagree

Reason for disagreement: While the UG does mention that users cannot add duplicate appointments, i feel that this fulfils the criteria of the second point qualifying it as a feature flaw, i.e. it could have been implemented to work better with little effort.

Apologies for the lack of explanation, but the purpose of the terminal output was to show the error caught being DuplicateAppointmentException (along with the stack trace), which I believe would have already been appropriately handled in other commands like add, with error messages being shown to the user.

As such, I believe it would not take much effort to replicate this code for the edit command. I think this change would result in significant improvements to the user experience, as the presence of an error would automatically prompt the user to check their input. Currently, without the presence of any error, users may be inclined to believe that the application is hanging or has crashed, as the command is also not automatically cleared but remains in the command input window. I assumed this was the case and restarted the application, only noticing the actual cause when I checked the terminal.

In summary, I believe the main issue is the application not doing anything when this error is encountered, leaving the user to figure out for themselves what the problem is, and I think that this lack of error can be resolved with already-existing code.

---

❓ Issue type

Team chose [type.FeatureFlaw]
Originally [type.FunctionalityBug]

• I disagree

Reason for disagreement: [replace this with your explanation]

---

❓ Issue severity

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

• I disagree

Reason for disagreement: Agree that in hindsight, this bug is definitely not High, but believe should be categorised as Medium instead. Reasons being:

1. Appears frequently rather than rarely. I think the target users would be constantly editing appointments based on new symptoms, medicine and even rescheduling.

2. Given the above, this would affect normal operations assuming users are constantly editing appointments.

3. Thus, believe this falls under occasional inconvenience, while users are able to continue using the product.

---