nus-se-script
commented
1 year ago Team's Response
Reason for response
- It actually works as expected. I feel it does not bring about the inconvenience that the tester has talked about: "I get a success message from the app again, without any warning or error that the task has already been completed... mistakenly marked the wrong task number when typing the command, which could definitely happen.". Our argument will be that the user can actually see that their task to unmark is not marked yet -- by seeing on the tasks panel that it is unmarked/ unchanged. But yes, it is still a valid functionality bug but does not justify the medium severity.
- Edit: Type changed to FeatureFlaw, due to being more of a flaw in the design, rather than an unexpected response with a functionality.
Items for the Tester to Verify
:question: Issue type
Team chose [type.FeatureFlaw]
Originally [type.FunctionalityBug]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
:question: Issue severity
Team chose [severity.Low]
Originally [severity.Medium]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
In this case, task 1 is already completed. But when i execute
mark 1on it again, I get a success message from the app again, without any warning or error that the task has already been completed.I would expect the app to instead show "This task has already been completed", as this would be helpful to remind the user if they maybe mistakenly marked the wrong task number when typing the command, which could definitely happen.