Description - Workfront built-in date fields all include time. This has an impact for users like us who only care about the date. The time component affects comparision and localtime conversion. We need a setting that allows us to control whether the built-in fields sets the time component or not, just like custom date fields.
Why is this feature important to you - The time component makes it difficult to compare if a date is <, =, > another date due to the time component. A task that should be marked as not overdue, will show as overdue if the date is the same, but the time doesn't match another date field. This is especially problematic for custom date fields that do not include time.
How would you like the feature to work - We need an option, probably per project and group, where the built-in datetime fields can turn of the time component (default to midnight). That way, when comparing date fields just for the date component, there is no comparison issue due to time.
Current Behaviour - A built-in datetime field sets the time to the moment the field is updated. The time impacts comparisions of dates (cannot ignore the time, even with the function to remove the time) and it impacts localtime conversion (the date can be off due to timezone difference).
