Pughal77 / pe

0 stars 0 forks source link

Error in the command summary table #4

Open Pughal77 opened 3 months ago

Pughal77 commented 3 months ago

Steps to reproduce: Copy paste the following input found in the add row of the command summary table

add n/James Ho p/22224444 e/jamesho@example.com a/123, Clementi Rd, 1234665 s/Maths l/Maths |2024-05-03|10:30

Expected:

Should not have l/Maths |2024-05-03|10:30 in the command input as you are unable to add a lesson to a student that does not exist.

add n/NAME p/PHONE_NUMBER e/EMAIL a/ADDRESS s/SUBJECT

Actual:

image.png

image.png

nus-pe-bot commented 3 months ago

Team's Response

Duplicated bug

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Incorrect example add command in command summary

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.


The example add command provided in the command summary is incorrect, as it includes the lesson field:

image.png

As expected, running the example command add n/James Ho p/22224444 e/jamesho@example.com a/123, Clementi Rd, 1234665 s/Maths l/Maths |2024-05- 03|10:30 does not work as the group has already specified earlier that one may schedule a lesson for a user together with its addition.

This is also specified in the error message shown in the application:

image.png

As the command summary is expected to be correct and new users who are unfamiliar with the product would definitely refer to it for examples of correct commands, this is a fairly serious error and hence I am assigning this a severity of Medium.


[original: nus-cs2103-AY2324S2/pe-interim#4687] [original labels: severity.Medium type.DocumentationBug]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

No details provided by team.

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)

Reason for disagreement: [replace this with your explanation]


## :question: Issue severity Team chose [`severity.Medium`] Originally [`severity.Low`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]