nus-se-script
commented
1 year ago Team's Response
A similar issue has been brought up about tags prohibiting whitespace as a parameter.
Fixing the ability to have white space in tags would solve this problem. As such, we have tagged this as duplicate.
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Tags prohibits space
tags do not accept spaces in their string. This can affect the user experience occasionally as some tags need spaces (Final exam)
[original: nus-cs2103-AY2223S2/pe-interim#1045] [original labels: type.FunctionalityBug severity.Medium]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
While this is definitely a nice to have feature, we think it's out of scope as it's additional functionality that is not that important. If a user wants to add t/Final Exam they can just add it as one word t/finalExam (i.e. use camelCase). This feature is not as important as what we have currently implemented and the functionality can be achieved in the current state.
We label this as low severity as this should not cause much inconvenience to the user to use camelCase or any other equivalent typing method with no spacing between words.
Items for the Tester to Verify
:question: Issue duplicate status
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
- [x] I disagree
Reason for disagreement: [This is not a duplicate bug. The first bug relates to the fact that you cannot add white spaces. The second bug relates to the fact that the error message doesn't show the error. The fact that one solution solves 2 problems doesn't make the 2 problems the same.]
## :question: Issue response Team chose [`response.NotInScope`] - [x] I disagree **Reason for disagreement:** [This is definitely within scope. Showing error messages that don't show the actual error affects the user detrimentally. especially for bugs that are caused by non-obvious and completely normal input that the user might enter. Also, it doesn't make sense that both bugs are declared NotInScope when they say they can fix it with one solution.]
## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** [Showing error messages that don't show the actual error affects the user occasionally. especially for bugs that are caused by non-obvious and completely normal input that the user might enter such as "Final Exam".]
When tags have spaces in their String, the application gives this error which doesn't show that the error actually is. This can affect the user experience occasionally as some tags need spaces (Final exam) and the user will think he is following the guidelines from the error message