nickeltea / pe

0 stars 0 forks source link

Command does not work as described by ug #8

Open nickeltea opened 1 year ago

nickeltea commented 1 year ago

image.png

The given example command as can be seen in the screenshot above cannot be executed.

Since the feature does not work as specified, this is a funcitonality bug.

nus-pe-script commented 1 year ago

Team's Response

Hi, thanks for the bug report!

This is indeed a bug. However, we feel it is a documentation bug as our UG misses to include the -n flag before the name.

Try running edit task 1 -n "Merge PR" -a 1 -d 2022-12-02 23:59 and it should work!

Changing the bug type to documentation to reflect to the same.

Also, it is a low severity bug because our app prompts the user to run edit task --help which shows the correct format for using the command :) Here's what it looks like: (notice that the help message shown includes the -n tag and the correct format) Screenshot 2022-11-12 at 5.44.45 PM.png Screenshot 2022-11-12 at 5.44.08 PM.png

Have a nice reading week ahead!

The 'Original' Bug

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

The edit task command example given in the user guide does not work as described

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.


image.png

As can be seen in the screenshot above, the command "edit task 1 "Merge PR" -a 1 -d 2022-12-02 23:59" is provided as an example but is unable to execute despite a valid task index being provided.

The user guide is innacurate.


[original: nus-cs2103-AY2223S1/pe-interim#3643] [original labels: type.DocumentationBug severity.Low]

Their Response to the 'Original' Bug

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

Hi, thanks for the bug report!

We accept this bug :) Good catch! (We missed the -n flag)

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 type

Team chose [type.DocumentationBug] Originally [type.FunctionalityBug]

Reason for disagreement: [replace this with your explanation]