Past/future restrictions on date fields
1) What is your original issue/pain point you want to solve?
Date attributes accept any date; there is no built-in validation window.
2) Which are one or two concrete situations where this problem hurts the most?
A “date and time of the event” field must not lie in the future, while planning fields like deadlines must not lie in the past. Today bad data has to be caught manually after the fact.
3) Why is it not solvable with the Zammad standard?
Date/datetime attributes have no validation options, and Core Workflow cannot restrict a date picker range either.
4) What is your expectation/what do you want to achieve?
Per-attribute options to allow/disallow dates in the past and in the future (e.g. “allow past: yes, allow future: no”).
Ticket#10231017