Tasks in ajax client for 5.0.7 require dates?

[bmdesmet]

Since the upgrade to 5.0.7, it appears that I can not NOT have start and end dates on tasks that I edit. The quick task create bar in the task view works as expected and quickly creates a task in the current task folder. As soon as I open any task however, it will fill in the start and end date (if none is already selected) with the current date. Attempting to delete those fields and saving brings up the error

"Cannot save. You have errors that must be corrected:
Invalid dates (make sure end date/time is after start date/time)."

The same error occurs if you create a new task and attempt to save it without start and end dates.

This is occurring with current IE7, Firefox 2.current and Firefox 3.current.

Are others seeing this and/or have I missed the bug on the matter?

[NoDoze]

Yes, in 5.0.7 you must enter a start date.

I too wish this wasn't changed. Cause I have tasks listed which I don't plan to start anytime soon, nor do I know when I will start them, I only know that I have to do them.

[mmorse]

Vote for / support ticket tag / CC watch: Bug 29221 - Tasks - don't require end date

[NoDoze]

It's not the end date thats a problem, but also the start date... Why is it required that there be a start date?

[bmdesmet]

Zimbra is apparently conflating end date and due date into one field; which is bad. There are plenty of instances when the end date could be after the due date. There is a similar matter with requiring the start date to be before the due date. I have certainly had plenty of tasks where I didn't start the task until after it was due.

The simplest solution would be to rename due date to end date as that is what is currently functioning as.

As to the matter of requring a start date or end date, I can not fathom why this is a good thing.