Different tag capitalisations causes tag commands to fail

[caipng]

Steps to reproduce

At least 2 persons

Part 1:

1. tagall sometag
2. tagall someTag
3. replacetag someTag sometag

Part 2:

1. untagall someTag

Expected

Part 1: All contacts will now only have sometag. The tag someTag should be gone.

Part 2: The tag someTag should be gone for all contacts.

Actual

Part 1:

Only the first contact has his tag replaced, the second still has the old tag.

Part 2: The console says that someTag has been removed, but the UI shows that the tag is still there

[nus-pe-bot]

Team's Response

Our team accept it as a bug. This issue is caused by having the same name tag which most contact usually do not have. This issue should not affect most users.

Items for the Tester to Verify

:question: Issue severity

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

• [x] I disagree

Reason for disagreement: I disagree with the downgrade of severity from Medium to Low.

Here, your team has claimed that such tags are a feature of your product.

With the assumption that such tags are allowed and your team has developed the app with this in mind, these bugs shouldn't be of low severity:

• It does not appear "only in very rare situations". Especially with commands like tagall that allow the user to tag contacts not within view, it is very easy to end up with such tags. The user can very easily enter the tag as CS2040 instead of cs2040 and end up with contacts having both cs2040 and CS2040. When such tags exist, even basic usages of the tag commands fail, as demonstrated.

• It does not only cause a "minor inconvenience". Should the user end up with such tags, it is very difficult to rectify and fix their mistake. As demonstrated, trying commands such as replacetag and untagall to remedy the situation simply don't work for such tags. Hence, it is is quite a headache to revert this operation. The user may even need to go into the json file to fix this, which is not just a minor inconvenience.

Hence I maintain that this bug causes "occasional inconvenience" when the user erroneously enters a slightly different capitalisation for tags, which would give this bug a severity of Medium.

---