Open joel-foo opened 10 months ago
We intended it this way as it is unsafe to have the appointments deleted along with the person. If a person is accidentally deleted and the user closes the application, they will lose all that person's appointments. Therefore, we require users to manually delete the appointment once it is completed or when the related person is deleted.
It also mentioned inn the UG that such operation that this is the expected behaviours.
Team chose [response.NotInScope
]
Reason for disagreement: - This issue is clearly not out of scope. Even though it is possible to delete the appointment once it is completed or when the related person is deleted
, lacking the ability to remove all of a person's associated appointments when that person is removed severely hinders the efficiency of the clinic administrators and can be considered a feature flaw. As an app designed to boost efficiency in managing appointments, lacking such a key functionality in the delete command clearly runs contrary to that aim and I feel it's a great setback to the users each time they have to perform this command.
It also mentioned inn the UG that such operation that this is the expected behaviours.
: As mentioned, I have tagged this as a feature flaw, not a bug. What you're mentioning here is only applicable to bugs.
Deleting a person but not their appointment does not fulfil an important need of the target user of an admin assistant. As an admin assistant handling medical records, if a patient is done, their appointments should be cleared, or else the appointment panel would be extremely cluttered. Imagine if each patient has lots of appointments, and if it is not cleared over time, it could lead to poor performance in the app.