Open nus-se-script opened 1 week ago
Thank you for testing ClientGrid.
Steps that led to this issue:
The bug is deemed a possible issue, and is considered response.NotInScope.
It is only a possible issue, not a confirmed one, as ClientGrid allows for meetings with properties that has been deleted intentionally as it understands that the meeting was created during a point of time where all the buyer, seller, or property involved in this meeting existed.
This behaviour is useful to users who want to use the meeting book as a means to store a record of scheduled meetings, even if the buyer/seller involved was deleted (perhaps due to the seller no longer willing to sell).
We do not want the features to be less useful than they can be.
Therefore, there is currently no feature or mechanism available to delete the meeting as well. This satisfies: 2) The user cannot attempt to use the missing feature. And thus it is response.NotInScope. Whether there should be a feature or mechanism available and its proper behavior would be debated in future iterations of the product.
Additionally, this issue is classified as severity.Low as it is unlikely to affect normal operations of the product. Appears only in very rare situations (of the user deleting the buyer/seller related to a scheduled meeting) and causes a minor inconvenience only (the user can still check through the meeting book and delete the meeting themselves, if they want to).
This is the same issue as bug #1518, which also deals with meetings not getting deleted after buyer/seller involved is deleted.
Duplicate of #1518
After delete seller with phone number: 34444444, the meeting with the seller with phone number:34444444 is still there, but in UG the meeting can only include phone number of existing sellers in the client book.
[original: nus-cs2103-AY2425S1/pe-interim#3238] [original labels: severity.Medium type.FunctionalityBug]