search

yucheng11122017 / pe

0 stars 0 forks source link

Vague instructions on find #3

Open yucheng11122017 opened 2 years ago

yucheng11122017 commented 2 years ago

According to the UG, it seems as though find can only be used for name or tag or platform and not concurrently. However, it actually works. Eg. find Alex t/Family No specification on how it works or if it can even be used. image.png

nus-se-script 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]

Mention that the search is an AND search

Documentation bug: reader does not know if the search is AND or a OR serch sicne it is not mention in the UG. For example, adding add n/Tan Yeoh p/187438807 t/friends fb/alex.yeoh ig/alex.yeoh tele/alyeoh tiktok/alex.yeoh and searching find Annie Yeoh returns none, even though there are people called Annie and Yeoh in my address book.

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

Their Response to the 'Original' Bug

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

We thank the tester for the bug report, and recognise that the phrasing in UG might have caused confusion.

However, we would like to point that most apps on the market use AND search. Also, AND/OR search might sound too technical for the average user.

Hence, we would like to argue that the bug is of very low severity instead.

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: The issue I am trying to bring up is not about the AND or OR search. It is about the fact that it seems like only flag can be used in each search Eg. find p/{platform} or find t/{tag} However, in reality, find {name} p/{platform} t/{tag} works for SociaLite but there is no mention of that in the UG. Users would not know about being able to do this.

:question: Issue severity

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

Reason for disagreement: Definitely not just a cosmetic issue. This is missing documentation on a whole functionality of a command.