search

harithh07 / pe

0 stars 0 forks source link

Leaves field is compulsory in Add Command but stated as optional in UG #8

Open harithh07 opened 2 weeks ago

harithh07 commented 2 weeks ago

UG states that the "leaves" field in Add Command is optional, however when adding a contact without a /l field, it throws an error.

Screenshot 2024-11-15 at 4.48.08 PM.png

Screenshot 2024-11-15 at 4.48.42 PM.png

soc-pe-bot commented 1 week ago

Team's Response

Thank you for your feedback.

We have classified this as a duplicate of #3860 as fixing the User Guide as required by #3860 will solve this issue too.

Thank you for your feedback. We would like to point out that the error message is already changed to reflect that fields "d/" and "l/" are required, hence the classification of the bug should be type.DocumentationBug as changing the user guide would solve the bug. Since users are easily able to figure out the right input from the error message, the impact should be severity.low.

The 'Original' Bug

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

"add" command format in app does not match format given in User Guide

In the User Guide, it is indicated that t/, f/, d/ and l/ fields are optional as seen by the square brackets encasing them.

image.png

However, if I enter just the required fields as stated in the User Guide, an invalid command format is shown to the user.

image.png

Upon further testing, fields "d/" and "l/" and required, which is different from the format stated in the User Guide.

[original: nus-cs2103-AY2425S1/pe-interim#3644] [original labels: severity.Medium type.FunctionalityBug]

Their Response to the 'Original' Bug

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

Thank you for your feedback. I would like to point out that the error message is already changed to reflect that fields "d/" and "l/" are required, hence the classification of the bug should be type.DocumentationBug as changing the user guide would solve the bug. Since users are easily able to figure out the right input from the error message, the impact should be severity.low.

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]