findCommonTiming - unexpected output

[pnutzz-0207]

UG did not specify what happens when multiple tags given in findCommonTiming.

When findCommonTiming t/friends t/family da/2022-04-16 given, the output is:

Only the last tag given is taken into consideration.

[nus-se-script]

Team's Response

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

The 'Original' Bug

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

UG - not detailed enough for findCommonTiming

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.

---

UG did not specify what will happen when multiple tags are entered. Actual result is that only the last tag will be processed.

---

_{[original: nus-cs2103-AY2122S2/pe-interim#2851] [original labels: severity.Low type.DocumentationBug]}

Their Response to the 'Original' Bug

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

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

Items for the Tester to Verify

❓ Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

• I disagree

Reason for disagreement: [replace this with your explanation]

---

❓ Issue response

Team chose [response.Rejected]

• I disagree

Reason for disagreement: [replace this with your explanation]

---

❓ Issue type

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

• I disagree

Reason for disagreement: [replace this with your explanation]

---