search

JunWei3112 / pe

0 stars 0 forks source link

The example command provided for the `status` command does not work #4

Open JunWei3112 opened 2 years ago

JunWei3112 commented 2 years ago

Screenshot 2021-11-12 at 4.42.29 PM.png

The example command given in the error message is status 1 approach. The expected behaviour is that this command should work, since it is given as an example. However, the actual behaviour is that it does not work, which mislead users and may confuse them.

I've given this a Medium severity level since it may be quite often that users refer to this error message when they accidentally entered an invalid status command, and since the example given does not work, it may cause them some inconvenience.

nus-pe-bot commented 2 years ago

Team's Response

No details provided by team.

The 'Original' Bug

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

Example given in status error message causes an error

Attempting to use the example command in the error message of the status command gives an error

Expected: No error, changes status to approached

Actual: Error message, invalid command format Screenshot 2021-11-12 at 4.53.06 PM.png

[original: nus-cs2103-AY2122S1/pe-interim#4005] [original labels: severity.Low type.FunctionalityBug]

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.Low] Originally [severity.Medium]

Reason for disagreement: I still feel that this is of a Medium severity level, since users may refer to the message for this command format quite a lot, since there are quite a long list of statuses that the user may not be able to remember. As such, users trying to execute the example command to test if the command works does not appear to be very rare, which is what a Low severity level bug is. This will also cause inconvenience to the users since they will not be sure if the status command is indeed working, or if their app is flawed since the status 1 approach command should be working on their end (since the developers did provide this as an example command, and so the command should be working)