kengjit / pe

0 stars 0 forks source link

UG - List did not mention about multiple flags #11

Open kengjit opened 2 years ago

kengjit commented 2 years ago

In the code, there could only be 1 flag type per command, meaning "--type todo --type deadline" to list all Todos and Deadlines is not permitted.

Perhaps this could be implemented in the UG.

soc-pe-bot commented 2 years ago

Team's Response

  1. Incorrect reporting of bug as FeatureFlaw instead of DocumentationBug in the Part II (Evaluating Documents) stage of the PE. Also, the team never cleimed that you can list multiple types at once.

image.png

image.png

Not that our UG says that there can only be one type that must be selected for the flag.

image.png

We also have specified when multiple flags can be accepted where supported so we do not believe that this is a valid issue as we DID NOT specify that multiple flags were accepted for this command.

The 'Original' Bug

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

List - Using multiple flags

Input: list --type deadline --type todo

Expected: List out all deadlines and todo

Actual: Lists out only todo

image.png

image.png


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

Their Response to the 'Original' Bug

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

UG does not specify that multiple filters could be used. Neither was it in our project scope.

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: Although it was not stated in your UG that multiple filters could be used, it would probably be helpful to include a note or a warning for the users. This instead is a mixture of both a feature flaw and documentation flaw.

Feature flaw: Would have been a reasonably useful feature and could be easily implemented.

image.png

Documentation Bug: If the feature is not implemented, but is fairly intuitive for the user to try it, it probably would be best to include a note to let the user know.

image.png

image.png

Therefore, they are different issues.


:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: Although it was not stated in your UG that multiple filters could be used, it would probably be helpful to include a note or a warning for the users. This instead is a mixture of both a feature flaw and documentation flaw.

Feature flaw: Would have been a reasonably useful feature and could be easily implemented.

image.png

Documentation Bug: If the feature is not implemented, but is fairly intuitive for the user to try it, it probably would be best to include a note to let the user know.

image.png

image.png


:question: Issue type

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

Reason for disagreement: [replace this with your explanation]


:question: Issue severity

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

Reason for disagreement: Although it was not stated in your UG that multiple filters could be used, it would probably be helpful to include a note or a warning for the users. This instead is a mixture of both a feature flaw and documentation flaw.

Feature flaw: Would have been a reasonably useful feature and could be easily implemented.

image.png

Documentation Bug: If the feature is not implemented, but is fairly intuitive for the user to try it, it probably would be best to include a note to let the user know.

image.png

image.png

Thus, this Is beyond just a cosmetic issue, at best this would be a 'severity.Low'.