Open nus-se-script opened 1 week ago
We have currently implemented it this way in order for it to work easily with our find command. We decided that the effort needed for allowing case-sensitivity for tags was not worth it and could be channelled to improving more significant areas of the find, add, edit and assign features and the tagging system. However, it is a good suggestion to allow greater flexibility in aligning with real-world situations, hence we have accepted the bug as not in scope
to work on it in future versions.
--
It was stated that the tags are case-insensitive in the UG. This means that the tag "1a" is treated equally to the tag "1A". Within the context of clinical study, there could be a situation where these could mean two different things. As such, it could confusion to the user.
In the planned enhancements, it was stated that it would allow special characters. Perhaps, the tags could be made case-sensitive to allow for more flexibility as well.
I have placed the severity as low as it does not affect much operations.
[original: nus-cs2103-AY2425S1/pe-interim#3458] [original labels: type.FeatureFlaw severity.Low]