nus-se-bot
commented
3 years ago Team's Response
This is intended behaviour. It is meant to be the timestamp of the log.
We intentionally did not add the feature of allowing users to add thier own custom timestamp as we want to cultivate a habit for users to log immediately after they have done their exercise. Also, if we allow users to input their own date and time, they can easily abuse their log.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: I would like to counter the team's response.
I accept that this is the intended behavior but there should be a mention of these somewhere. Especially "cultivate a habit for users to log immediately after they have done their exercise". However, having said that, the value of their application would have been lowered as it is not very reasonable for a typical user to exercise with their laptop/desktop since this app is still not available on mobile devices. Shouldn't the prevention of abuse be mentioned as well since it's a major feature of this app? A user should get into this app knowing that the logs are not to be abused and have the determination so that at least they can expect the datetime to be unmodifiable.
I feel that these are not very convincing reasons because their app is meant to make "tracking your progress" "easier" but the potential frustration from unexpecting users can already be imagined. They are signing up for an app that could be their "partner in helping to change their life" but it turns out to be a rigid diary that disallow backlogging. The time that each entry is stored quickly become useless if it was not consistently used to log exercises immediately after their exercise.
In addition, there is less benefit to restricting recording of logs in real time (and not able to modify it) as compared to exam sessions or quiz. This is especially for tools like a diary where users should be allowed to backlog their entries. If it was even mentioned in the brief app description that the app is meant for immediate recording upon of completion of exercise, then maybe this app would be of some use. But in actual use cases, not many people would keep their laptop on while they are exercising just to log it in real time. If they miss recording by a day then it just screws up their progress logging with little ways to revert other than hackish methods like changing system time.
Therefore, I stand by my decision that this feature flaw is one that "affects most users and causes major problems for users." Datetime is a fundamental feature that should at least be explicitly mentioned to users.
I even looked through their user stories again and there is no use case where the team states that users would like to record their exercises immediately or in real time. Neither is there anything on datetime which I would consider a lack of consideration regarding this aspect.
Datetime is a field but there is no way to modify the datetime. This is a huge feature and functionality flaw that the app is introducing, the user may choose to pre-recorded or post-recorded the exercise but it is saved according to time the log was added. There should be an option to edit the datetime, or at least include in the UG that it is the datetime the log is added and user should use comments instead.
However, it can get messy and confusing if users can only use comments to denote the date when a user is not specifically restricted, especially when a user wants to do backlogging for the previous day or week.
://raw.githubusercontent.com/jeffreytjs/pe/main/files/2d8f7d72-7b5d-452e-a996-1303560c80d3.png)