nus-pe-bot
commented
2 years ago Team's Response
The tags feature works as expected as described in the UG, where it states there cannot be spaces between words and it must be alphanumeric.
Furthermore, the intention of the Tags feature is to store 1 word descriptions, whereas the Notes feature allows for the user to keep more information they wish about the applicant.
If you wish to add more information about the applicant, you should utilize the Notes feature (as it is intended to be used) and it will also be present on the GUI as well.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: Hi, thank you for the explanation. I roughly see the design choice made here, but I feel that it is an unreasonable constraint as it can be easily changed by modifying the validation function a little.
I suppose that the design choice was made such that any additional information will be added to the notes section, but it feels like small tidbits of additional information such as the programming language someone is proficient in should be added via tags. This avoids cluttering the notes section, if some other additional info is needed in the notes section, as seen here:
vs
:question: Issue severity
Team chose [severity.Low]
Originally [severity.Medium]
- [x] I disagree
Reason for disagreement: This feature is a rather major part of the program and as seen in the scenario I provided during the PE, it can be a rather frequent occurrence. I could even argue that it may be a high severity bug given how frequent it occurs.
Tags should allow multiple words, or even special characters. For example, consider cases where you are a recruiting for software engineers, and you want to tag people based on the language they know/experience they have. You won't be able to tag someone with "c++", nor "ruby on rails".