KT27Learn / pe

0 stars 0 forks source link

Find command inconsistent in matching tag fields #6

Open KT27Learn opened 3 years ago

KT27Learn commented 3 years ago

Currently the find command works mostly as stated except when it comes to matching tags. As shown below, when I am trying to find contacts with hackathon2021 tag, it should show the first person on the list. However, no results were shown when the command was entered.

Screenshot 2021-11-12 at 5.00.27 PM.png

Screenshot 2021-11-12 at 5.00.33 PM.png

nus-pe-bot commented 3 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]

find function based on tags is slightly buggy

I have two profiles with the tags "hackathon" linked to it but when i type "find t/hackathon" only returns one instead of two.

The hackathon tags are of two different colours, not sure if they are meant to be that way.

First profile

image.png

Second profile

image.png

After typing find t/hackathon

image.png


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

Their Response to the 'Original' Bug

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

In the User Guide, it is mentioned that there are 3 types of tags (General, Event, Module), and their respective prefixes. The find command matches the tag exactly. So users need to include the type prefix. hackathon is an Event tag. The tester should have entered find t/event-hackathon instead. Since find t/hackathon was entered, it would only show contacts with hackathon as a general tag.

image.png

Screenshot 2021-11-13 at 5.54.59 PM.png

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 reason]


:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: [replace this with your reason]


:question: Issue type

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

Reason for disagreement: [replace this with your reason]