soc-pe-bot
commented
1 year ago Team's Response
This bug report is rejected, as this functionality is clearly implemented in the remove command. As such, the tester's claim that "he needs to delete the entire Person. This will be very very inconvenient, hence this will be a medium bug." is invalid, as there is no need to delete the "entire Person" every time the user wants to remove optional fields.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: Okay, I see.
But using another command removepj is difficult and might not be optimised for fast typists in the command line.
Hence, I think my bug should not be rejected, but I agree that it can be a feature flaw.
## :question: Issue type Team chose [`type.FeatureFlaw`] Originally [`type.FunctionalityBug`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
In the UG, for the 'add' command, it is shown that every other command flag is optional except for name. Hence, I should be able to set the other optional fields to nothing.
This input validation makes it hard to get rid of the optional fields. If the person input a wrong phone number, and wants to set it to nothing again, he needs to delete the entire Person. This will be very very inconvenient, hence this will be a medium bug.