Check, add and update inconsistency

[nicknamenic]

If I cannot add or update an activity to a past date, then it is inconsistent to allow for checking of future activities, since the intended usage for checking is to mark which activity is done. If anything, past dates should be allowed to be inputted, if the user wants to keep track of previous activities.

[nus-se-script]

Team's Response

The travel planner is for planning future activities. Once you have completed the activity, then you check if off. It does not make sense to include an activity that you did not plan on doing in the first place after the date you specified is over.

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

• I disagree

Reason for disagreement: This is an example of overzealous input validation, i.e. there is no reason to not let users input past dates (for record keeping), since it would add nothing but value to the program. Instead of acceptance, however, maybe this should be NotInScope instead, or the bug severity toned down to low.

---