nus-se-bot
commented
1 year ago Team's Response
This seems to be a duplicate of #130: Use case 2 Extension 3a possible incorrect flow as removing extension 3a completely under the "Remove a batchmate" use case to resolve #130 would also automatically resolve this issue (#129).
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Use case 2 Extension 3a possible incorrect flow
Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.
In use case 2 extension 3a, the use case resumes from step 4 although an incorrect value was given; according to the app's behaviour, it does not delete a batchmate (after the warning is given) if an invalid value is given in the command.
[original: nus-cs2103-AY2223S1/pe-interim#169] [original labels: severity.VeryLow type.DocumentationBug]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
Good catch!
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]
Under the DG use case 2 Extension 3a, removing a batchmate (Delete command) only requires an index as a parameter, but the extension states that an incorrect phone number is detected in the command.