pnutzz-0207 / pe

0 stars 0 forks source link

viewGroup - unexpected result when multiple tags given #4

Open pnutzz-0207 opened 2 years ago

pnutzz-0207 commented 2 years ago

The UG did not specify what will happen when multiple tags are entered after viewGroup. Users do not know what to expect.

Expectation 1: error message pops out Expectation 2: Shows all users that attaches to the tags given

Actual: Only the tag at the last will be given. For example:

Screenshot 2022-04-16 at 2.41.22 PM.png

nus-pe-script commented 2 years ago

Team's Response

image.png

Note the third point and the fifth point of this section of the UG. As there is no ... in the viewGroup explanation (see screenshot below), only the last tag should be considered, which is the expected behaviour of UniGenda.

image.png

The 'Original' Bug

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

UG - viewGroup not detailed enough

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.


The UG did not specify what will happen when multiple tags are entered. The actual output is that only the last tag given will be processed. Screenshot 2022-04-16 at 3.18.57 PM.png


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

Their Response to the 'Original' Bug

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

image.png

Note the third point and the fifth point of this section of the UG. As there is no ... in the viewGroup explanation, only the last tag should be considered, which is the expected behaviour of UniGenda.

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 response

Team chose [response.Rejected]

Reason for disagreement: [replace this with your explanation]


:question: Issue type

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

Reason for disagreement: [replace this with your explanation]