Unset the new trip form's "ends at" date field, to allow users to select any starts at date
Details
A current point that users find difficult is that by default they fill form steps top to bottom. The step where you define when the trip starts and ends commonly causes issues. The default values for these fields are today and today + 7 days. (The value of these default field values are contentious other than for showing that the field's data type is a date, but that's beside the point.)
The end date validation means that when the user goes to set the start date of a trip, they are limited to any date within 7 days. They then have to go and clear / set the end date in order to set the start date.
Proposing either to not set either field by default, or just set the start date to today and don't set the end date
Who would benefit from this?
All users creating trips
Please check the following
[X] If this feature is implemented, I won't be compensated for it and I don't own any rights or stake in the feature
[X] I've checked the other feature proposals and nobody has posted this already
Summary
Unset the new trip form's "ends at" date field, to allow users to select any starts at date
Details
A current point that users find difficult is that by default they fill form steps top to bottom. The step where you define when the trip starts and ends commonly causes issues. The default values for these fields are today and today + 7 days. (The value of these default field values are contentious other than for showing that the field's data type is a date, but that's beside the point.)
The end date validation means that when the user goes to set the start date of a trip, they are limited to any date within 7 days. They then have to go and clear / set the end date in order to set the start date.
Proposing either to not set either field by default, or just set the start date to today and don't set the end date
Who would benefit from this?
All users creating trips
Please check the following