Activity Scheduling: Schedule time cannot be in the past

[anantmittal]

Issue:

Right now people can’t schedule an activity on a date that’s already passed. However, they can schedule an activity that happened earlier in the day. For example, at noon, I can schedule an activity at 11am. We should validate the scheduled time to be past the current time during scheduling.

[jayfo]

Discussed w/ Anant on 6/26. I'm unsure about this.

If I decide to do an activity today, then want to capture that in the app afterwards, I think I should be allowed to do that.

The current implementation also does not handle a case of repeating activities that include today but occur at an earlier time.

And of course both of the above could be true at the same time. I do an activity, decide I want to schedule it on a repeating basis, but then cannot because the time has already passed for today.

Overall I think this constraint might be too strict without clear benefit.

[jayfo]

To discuss w/ @garyhsieh. After that, decide whether to close (i.e., if this traced back to Gary) or to discuss with larger team (i.e., if this traced back to somebody there).