nus-pe-script
commented
2 years ago Team's Response
Hi, this is stated in the UG to warn off non advanced users who do not know how to deal with such editing. There is no constraints for users to edit the file because we are just offering a warning to the target users who may not be proficient in dealing with the technicalities.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: Although it is valid to warn non-advanced users who do not know how to deal with such editing, this has the side effect of excluding advanced users who might want to edit the file on their own, since the warning is not specifically targeted towards non-advanced users. If advanced users only learn about the app through the User Guide and get the impression that they cannot edit the file, they might choose another app instead due to the large amounts of data (e.g. large numbers of hall residents) that make manual editing more efficient.
In light of this, I agree to changing the nature of the bug to a type.DocumentationBug but not to its rejection.
:question: Issue type
Team chose [type.DocumentationBug]
Originally [type.FeatureFlaw]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
:question: Issue severity
Team chose [severity.Low]
Originally [severity.High]
- [x] I disagree
Reason for disagreement: Having agreed to changing this to a type.DocumentationBug, I think the corresponding severity should be severity.Medium. This is because users under the impression that they cannot edit the file at all would face inconveniences as they have to resort to a large number of commands to input information instead of just achieving the same outcome via manual editing.
tP constraints: json has to be editable
But UG states that json should not be edited