Open brelkh opened 2 years ago
Our appointment feature is meant to keep track of future schedules/meetings with the clients. Not to keep track of past appointments, by design.
Team chose [response.Rejected
]
Reason for disagreement: This is similar to "overzealous input validation" example 2:
Preventing me from keying in past dates is a hindrance and does not benefit the product in any way. This blocking did not need to be implemented (a warning would have sufficed) and was an incorrect design decision, thus, it is a feature flaw.
As a user, I may want to keep track of past appointment dates with buyers and sellers. However, this is not allowed as I can only assign future appointment dates.