Open nus-se-script opened 11 months ago
I understand your concern. However, as outlined in our User Guide, the purpose of our tagging feature is to help categorize
your friend with relevant tag and simplify contact management.
Since friend
and friend
is the same word and falls under the same category which is Friend
, hence we have labelled your friend with the Friend
tag, which is what the tag feature does and what the user want (label the student as their friend).
For the issue about friend and close friend, our app choose to differentiate 'friend' and 'close friend' into two different catogary. This is because different users have different preference,our app recognizes that users have diverse preferences.
While some may choose to tag a person as both a 'friend' and a 'close friend', others may prefer to use only one of these tags. This versatility is a key aspect of our app, designed to fully satisfy the varying needs of our users. Whether you want to categorize someone as a 'friend', a 'close friend', or both, our app supports these preferences, offering flexibility and personalized contact management. Hence, considering this flexibility and user-centric design, we do not see an issue with the current functionality.
Considering these aspects, we have decided to reject this bug report. We believe our tagging system aligns well with the intended functionality and user flexibility. We appreciate your feedback .
--
Entering "add n/Ben p/00000000 t/friend t/friend" only adds one friend tag to ben, but entering "add n/Ben p/00000000 t/close friend t/friend" adds both tags to abc. Allowing multiple tags serves no purpose as it does not make sense for users to tag someone as both a friend and close friend.
[original: nus-cs2103-AY2324S1/pe-interim#5198] [original labels: type.FeatureFlaw severity.VeryLow]