Open jonasgwt opened 1 year ago
It is not a bug, because we deliberately design the tag to be able to differentiate between case-sensitive words. For example, a user might have a pool of contacts to watch a sitcom called "Friends" together and want to have tag "friends" for the user's actual friends. Hence why they are interpreted differently. That's why in our UG, we never say that tag is case-insensitive.
Team chose [response.Rejected
]
Reason for disagreement: Although there is a genuine use case that the team has mentioned, the problem that a user might mistakenly add a similar tag but of a different case still remains a very real problem. To cater to both use cases, a warning, as indicated in the title of the bug report, should be the expected behaviour of the application.
Team chose [type.FeatureFlaw
]
Originally [type.FunctionalityBug
]
Reason for disagreement: [replace this with your explanation]
Team chose [severity.Low
]
Originally [severity.Medium
]
Reason for disagreement: [replace this with your explanation]
Steps to reproduce:
Execute
tag add 2 t/Friends
to person at index 2 who already has tag friendsExpected Output:
The contact already has the tag
Actual Output:
The tag is added. The person now has 2 tags called friends
Screenshots: