soc-pe-bot
commented
2 years ago Team's Response
Thank you for your input. We do take into consideration of having tag list command in the feature in our future iterations. But the reason why we put it as low is because when the user creates a tag, it is most likely added into the contact and todo, therefore user will be able to easily refer to what tags have been used in the contact and todo list. Moreover, it also does not affect the app workflow.
Items for the Tester to Verify
:question: Issue severity
Team chose [severity.Low]
Originally [severity.Medium]
- [x] I disagree
Reason for disagreement: Responding to user will be able to easily refer to what tags have been used in the contact and todo list: if a user only have 1 person with a particular tag, and he has 200 persons in total, it is way too hard to eyeball for that tag one by one.
Second, the user may not always enter the tags directly (having second thoughts). He might forget about some particular field of the person.
And another case is when a user deleted all persons of a particular tag (e.g. housemate). Then after a few months, he get a new set of housemates, but he forgot how was the housemate tag written(house mate, housemates, Housemate). As a result, he needed to do some trials and errors before getting the correct one.
It would be a lot better if you can just allocate some part of the GUI for the tag list, as the benefits will definitely outweigh the small additional effort needed.
At this point, there is not tag listing command. But as a user, it should be one of the most important tag commands, as I would want to know what tags do I have right now. If not, I might have to do trial and error every time I add a new person with a tag, which may slow me down.