nus-pe-bot
commented
2 years ago Team's Response
This is an implementation choice, as seen by the fact that other commands support the auto-date/time it was indeed possible to implement it to schedule as well.
For recording of meals, fluids, weights, workouts the usual behavior is to record something that just happened, with the additional ability to record entries in the past (in case you forget).
However for scheduling, the usual behavior would in scheduling something in advance, in other words the future. As such this auto-date/time is not supported for the scheduling of workouts. This is because users may forget to enter a date or time when scheduling and the entry would still record successfully, where they may not have knowledge of their error if they do not check properly.
This compulsory date and time is also stated in the UG:
In short it is an implementation choice since the conventional behavior for scheduling is future-based unlike the other commands/features.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [ ] 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]
When scheduling a workout it does not automatically enter the current date or time if i want it every week at my current timing. Instead an error is thrown regarding file separator which is irrelevant.