nus-pe-bot
commented
7 months ago Team's Response
No details provided by team.
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Incorrect phrasing of add use case
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 step 1a2 it is not necessary that the user immediately enters the correct command syntax. Perhaps step1a2 is removed and it is indicated that steps 1 are repeated
[original: nus-cs2103-AY2324S2/pe-interim#3704] [original labels: severity.Medium type.DocumentationBug]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
Dear tester, we sincerely acknowledge this issue and we accept it, however, we would like to propose a change to the severity. <3
severity.Low : A flaw that is unlikely to affect normal operations of the product. Appears only in very rare situations and causes a minor inconvenience only.
We would like to change the severity to low because the error is quite minor; it can be resolved if we removed the word "correct":
1a System detects an error in entered command syntax 1a1. System requests for correct input 1a2. User enters command Steps 1a1 - 1a2 repeat until command syntax is correct use case resumes
Thank you
Yours Sincerely, JAYME
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: No proof given for why these are duplicates. Changing one use case does not affect the other. Moreover, they are clearly different commands and may affect different developers uniquely.
## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** This can cause the developer to be unsure what the exact app behaviour is, ie: should the app close if the user attempts incorrect/correct fields, or should they keep allowing the user to reattempt correct/incorrect commands. Keeping this in mind I believe that this would occasionally cause developers to have to double check the actual intended behaviour.
If user enters the correct tag in step 2a2. it is not necessary that the steps are repeated until the selection is correct. Moreover, it is not necessary that the tag added is correct.