Open kab-dot opened 2 months ago
for this use case, there could also be a case where the specific contact still has a log in the elderscrolls so their contact still cannot be deleted unless that log has been deleted so that use case is missing
We recognise that this is a valid concern, and that there could have been an additional extension that would make clear the requirement of a contact not being able to be deleted if they had an existing log.
However, we strongly disagree with the indicated medium severity of the bug. Given that we have already iterated and highlighted this requirement of a contact not being able to be deleted in the DG / UG multiple times, we believe that the issue is at max of low severity, since it is unlikely to hinder normal operations, and at most cause a minor inconvenience where a developer would refer to other parts of the documentations which explicitly specify this requirement.
Additionally, please refer: https://nus-cs2103-ay2324s2.github.io/website/schedule/week7/topics.html#requirements-specifying-requirements-use-cases-usage
Given that our DG covers an extensive number of use cases across a majority of our supported commands, we believe that it should be classified as NotInScope
, as while it is a valid issue, fixing it is less important than the work done in the current version of the product. Given that by CS2103/T guidelines, use cases have no strict rule about writing all details of a step, the exclusion of the said extension does not make our use case invalid nor wrong.
Team chose [response.NotInScope
]
Reason for disagreement: However, I still think that there makes a case as the delete function is quite important and having a complete use-case that goes through the step by step process would help the users out as compared to a incomplete one. I hope you can see where I'm coming from, especially since when I was going to delete the contact and realised there were extra things I had to delete alongside but weren't stated initially.