nus-pe-script
commented
1 year ago Team's Response
No details provided by team.
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Missing Use Case - Add Person
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.
Missing extension when the person is already added to TAB
[original: nus-cs2103-AY2223S1/pe-interim#694] [original labels: type.DocumentationBug severity.Low]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
There seems to be a mismatch between the title and the details.
Title says there's a missing Use Case for Add Person The use case is here:
The details says Missing extension when the person is ALREADY ADDED to TAB. Unsure of what this means. Do you mean the use cases of what a user can do after a student has already been added (eg, able to add assignments to them, able to add grades). In that case, here are 2 examples of the many we have:
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)
- [x] I disagree
Reason for disagreement: The bug I reported is about missing use case extension, the bug that is a "duplicate" is about missing use case for add person. These 2 bugs are different as such should be handled separately.
:question: Issue response
Team chose [response.IssueUnclear]
- [x] I disagree
Reason for disagreement: The team has a missing extension in the use case 03. It should be 1c. where the new students details are a duplicate of an existing student and thus a duplicate error should show and the use case ends. This case was not considered in your use case extensions.
In addition, as this is not a cosmetic bug, I would like to change the severity to low instead of very low.
There should be an extension where the user edits a name of a person but the name/ person already exists in TAB and this should also throw an error. This case is not considered in your extensions.