nus-pe-bot
commented
4 years ago Team's Response
This is a valid bug. However, we disagree with the severity 'High' because it is not causing the users to not be able to use the app at all or even frequently. In fact, it is a good mechanism (of truncating) that we did not mention in the documentation. Hence, we changed the label to Documentation bug and severity to low.
Items for the Tester to Verify
:question: Issue type
Team chose [type.DocumentationBug]
Originally [type.FunctionalityBug]
- [x] I disagree
Reason for disagreement: I feel that this bug does not relate to "a missing step, a wrong instruction, or typos that affect users", which is what documentation bugs are supposed to be about. In fact, my assessment is that this is indeed a functionality bug, as it relates to "a functionality does not work as specified/expected." Not only is this an expected behavior that the user anticipates (as explained in my issue), but this is indeed a specified behavior (see the response text returned by the app, as seen in the issue). It is clear that making certain edits to the documentation would not fix the issue. In order to do so, the developers would have to modify the response code in the app.
:question: Issue severity
Team chose [severity.Low]
Originally [severity.Medium]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
As shown below, the app specifies that the name can (and should only) contin alphaneumerics and spaces as shown below:
However, when the name of the group is started with a space, the spaces are truncated. This is not what I expected as shown below:
I think that if this is the behaviour, then it should be specified as it misleads the user.