Issue Summary

Date compare validator error for Custom fields with Date Time picker failing comparison with or without Include time part option enabled

Steps to Reproduce

1. On a workflow transition add a Date Compare Validator
2. Select a Date time custom field a condition great ">" or great equal ">=" to an expression like now or >= 1d

Expected Results

When the transition is triggered the validator respects the time and expression configured.

Actual Results

The date and time are not respected with several hours of difference, with or without the Include time part option enabled.

With the Include time part option enabled, it should respect a 24h difference, considering the hours the transition is triggered and the user timezone.

With the Include time part option disabled, it should respect the start of the next date 00:00:00, considering the date the transition is triggered and the user timezone.

If using an expression in the validator, for example <dateTimeField> is later than 2d - the validator will only work if a time value is selected, even if the date does not match the "later than 2d" validation. 

Workaround

The user in this case can use a date type custom field, so the start of day will be considered in the comparison.