Open leeyiheng12 opened 2 years ago
Accept this Bug. The intended behaviour of the Tags is to be case-sensitive and Priority Tags and Application Status Tags are case-insensitive. Due to a documentation error, the information presented was mixed which resulted in this bug being reported, as it is only under the edit command that we made the error of stating it is case insensitive, but under notes, it is stated that optional tags are case sensitive. But we will consider this a VeryLow Severity DocumentationBug.
Team chose [type.DocumentationBug
]
Originally [type.FeatureFlaw
]
Reason for disagreement: [replace this with your explanation]
Team chose [severity.VeryLow
]
Originally [severity.Medium
]
Reason for disagreement: "Very Low' severity bugs should only be bugs that are purely cosmetic and do not affect usage (for example a typo/spacing/layout/color/font issues in the docs or the UI that doesn't affect usage).
The error in the UG led to the user experiencing a different behaviour than expected. A user's usage would definitely be expected. Minor inconvenience is caused as the user would have to recheck the UG to double confirm, but the user can still continue to use the product after checking the UG and retyping the command with a minor change. According to the definitions given on the website, this would be a bug of medium severity.
To reproduce:
1) Type
add n/TestCompany j/TestJob15 p/1234 e/testemail@test.sg a/TestAddress(123456) pt/HIGH ast/ACCEPTED t/tagtest t/TAGTEST
Expected behaviour:
Only one tag present
Actual behaviour:
Two tags present, even though tags are meant to be case insensitive.