search

audipras / pe

0 stars 0 forks source link

Cannot create multiple aliases for the same tag name. #3

Open audipras opened 2 weeks ago

audipras commented 2 weeks ago

We should be able to create multiple aliases that net the same tag name. It makes sense for there to be multiple shortcuts since different people could have different shorthands for tags. (e.g. both "v" and "ve" for the tag "Vegan")

Steps to reproduce:

  1. Create an alias for a tag using the addShortCut command.
  2. Create a different alias for the same tag name.

Screenshots: After adding the shortcut "V" -> "Vegan": image.png

Attempting to add alias "ve": image.png

nus-se-bot commented 1 week ago

Team's Response

Thank you for your suggestion. We view the severity of the claim to be low as the feature "listShortCut" would show all shortcut mappings, which will eliminate any confusion regarding tagging using shortcuts.

However, we reject this issue as we still feel like our current design (assigning only one alias to one tag name) provides the most clarity and usability. Allowing multiple aliases per tag could result in an overly long mapping list, which may inconvenience users rather than help them.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: I disagree with the claim that it provides the most usability, since it is a restriction. Considering the context of a fast-paced restaurant environment where multiple different staff will be using this app, it makes sense to have multiple aliases mapping to the same tag since different staff will have different shorthands for the tags. Clarity is a fair consideration, however since configuration and learning of the shortcuts can take place outside of service periods, it is not a design decision in line with the context of a fast-paced restaurant environment. Speed, useability and reliability should therefore by the priority, and allowing multiple mappings would definitely increase the speed of use, useability and reliability (less mistakes made since multiple aliases could be accepted) of the application

## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]