Confirmation message shown in delete command even when no such person exsists

[kinjalagarwal1810]

Expected: An error to be shown when i want to delete a person with a id that is invalid

Acual: A conformation message is first shown if i want to delete the person with the id (that doesn't actually exist), then once i confirm i am shown an error that a person with that id does not exist.

This feels very redundant as if the person does not exist I should not need to confirm.

[nus-se-script]

Team's Response

Severity should be Low instead of Medium

• This bug causes only a minor inconvenience to the user as it does not cause unexpected loss of data and all behaviors are correct. It is unlikely to affect normal operations of the product. The only inconvenience they experience is an extra confirmation message that warn them that they are executing the delete function. In addition, this warning message may also be beneficial in situations where the user actually intended to use another command but typed delete carelessly instead. This can remind the user that the command he/she is trying to execute is a destructive action.

Bug Type should be FeatureFlaw instead of FunctionalityBug

• the behaviours are handled correctly and is in tandem with the UG, albeit there might be a more optimal order of handling the case where the person does not exist. Hence, it should not be a FunctionalityBug

• It should be parked under FeatureFlaw instead, as it is considered as the flaw that may not be optimised well enough

  Items for the Tester to Verify

  :question: Issue type

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

• [ ] I disagree

Reason for disagreement: [replace this with your explanation]

---

## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]

---