nus-se-bot
commented
1 year ago Team's Response
Marking a task as done allows the user to keep the done tasks present in their data files, for them to refer back to the task in the future. Perhaps this is subjective in terms of explanation, but our team feels there is no bug here. We agree with your benefit stated but we do not feel that our stated benefit is wrong.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: I understand where you're coming from but the benefit that you have stated depends on how the application is implemented. However, during the stage of creating user stories, the implementation of your application should not be present yet as the user stories are there to help you actually implement your application.
So it's like this benefit is not a direct consequence of marking tasks and deadlines as done. For your mentioned benefit, perhaps the user story of "... I want to keep completed tasks and deadlines stored so that I can refer to them in the future" will be better.
As seen in the screenshot, the highlighted feature of the app, which is marking tasks as done when completed, does not have a direct impact on allowing the user to refer to these tasks in the future. That may be a linked to another feature of the app that allows users to view all tasks that have been marked as done.
The more direct benefit will likely be for the user to keep track of which tasks have been completed so that they have a better idea of what tasks are still undone.