nus-pe-bot
commented
3 years ago Team's Response
find command searches a visitor in the tracking list. It seems that you cannot find a person in tracking list, which means that you have cleared your tracking list before. You can refer to the issue #676 as we deem that it is caused by the clear command mentioned in #676.
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Cannot checkin after clearing
Cannot checkin after Clearing, based on UG, it seems to mean clear everything, but program still keeps track of the past id's, which might be confusing.
[original: nus-cs2113-AY2021S2/pe-interim#676] [original labels: severity.Medium type.FunctionalityBug]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
clearcommand only clears tracking list and not the log file as stated in the FAQ section of the UG:
Therefore, checking in
checkin i/001D n/Tom p/12345678will lead to an error as the person with the same ID with a different name exists in the log file. However, we recognise that we were not clear about theclearcommand in the UG. Therefore we accept it as a Low severity of documentation bug.
Items for the Tester to Verify
:question: Issue duplicate status
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
:question: Issue type
Team chose [type.DocumentationBug]
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]
Seems to me the program keeps track of all history. Might want to be clearer on this as it is very misleading. Maybe could listall should include all id's from history.