search

weiquu / pe

0 stars 0 forks source link

MORE_INDICES for unmark command #6

Open weiquu opened 2 years ago

weiquu commented 2 years ago

It is told to the user the MORE_INDICES must be separated by a single space, but commands where they have multiple spaces still run (e.g. unmark 1 2 3 4)

soc-pe-bot commented 2 years ago

Team's Response

Our team feels that this should be classified as a documentation bug as it is only a mismatch between behavior and documentation. What needs to be updated is the UG phrasing. In fact, having multiple spaces actually helps in functionality. Very low severity as it is a typo. Does not affect intended usage in all cases.

Duplicate as targeting same typo in UG.

The 'Original' Bug

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

MORE_INDICES for mark commnad

It is told to the user the MORE_INDICES must be separated by a single space, but commands where they have multiple spaces still run (e.g. mark 1 2 3 4)

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

Their Response to the 'Original' Bug

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

Our team feels that this should be classified as a documentation bug as it is only a mismatch between behavior and documentation. What needs to be updated is the UG phrasing. In fact, having multiple spaces actually helps in functionality. Very low severity as it is a typo. Does not affect intended usage in all cases.

Duplicate as targeting same typo in UG.

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: As mentioned in the CS2103 website, bugs are considered duplicates if it is behaviour that is "caused by the same defect and cannot be fixed independently". However, in this case, the error is not the same typo and can be fixed independently. Furthermore, the error is for 2 different commands that are separate from one another, and thus the error is not a duplicate.

:question: Issue type

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

Reason for disagreement: [replace this with your explanation]

:question: Issue severity

Team chose [severity.VeryLow] Originally [severity.Low]

Reason for disagreement: I believe that the severity of the bug should be Low as it is not a "cosmetic problem" but rather a clear difference of meaning and intent that has been documented. The team has also acknowledged that it is a "mismatch" and hence is not merely a typo but a mistake in the documentation.

In addition, while the bug might not affect intended usage, it still appears in rare situations and can cause a minor inconvenience if the user believes that there must be only 1 space but has inputted multiple spaces, thus causing them to have to go back and remove the additional spaces (due to the mistake in documentation). Hence, the bug should be given Low severity.