Open ishan-agarwal-05 opened 4 days ago
[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]
Tags are meant to be unique including case-sensitivity to give the user flexibility to create or edit tags.
It is not part of the duplicated client or rental information detection as seen in the User Guide.
Therefore, severity is low because normal operations are not affected and only happen in very rare situations where users try to assign similar tags which only differ by one or some uppercases.
However, we believe it can be better, hence we will classify as NOT-IN-SCOPE instead of Rejected. It is a FeatureFlaw instead of FunctionalityBug because it is the intended behaviour, but we acknowledge that value could be added by limiting the case of tags.
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your reason]
Tags are case sensitive making tag1 and Tag1 2 different tags which should functionally be the same