Tickets :: [#5377] New Nag task form has problems with alarms and due dates

6.0.0-beta1

7/21/25

Summary	New Nag task form has problems with alarms and due dates
Queue	Nag
Queue Version	HEAD
Type	Bug
State	Resolved
Priority	2. Medium
Owners	jan (at) horde (dot) org
Requester	chuck (at) horde (dot) org
Created	05/19/2007 (6638 days ago)
Due
Updated	06/03/2007 (6623 days ago)
Assigned	05/23/2007 (6634 days ago)
Resolved	06/03/2007 (6623 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

06/03/2007 01:14:52 AM	Chuck Hagenbuch	Comment #7 State ⇒ Resolved	Reply to this comment
This is fine for me with today's changes.

05/25/2007 04:58:22 PM	Chuck Hagenbuch	Comment #6	Reply to this comment
I'd like to get the old due date interface back, though - it's a pain to have three clicks to get the date + time, and to have 5 clicks to go back to not having a due date. We can put it in a custom renderer like the alarms. It's two clicks if you use the date picker. And it wasn't really less clicks in the old widget, because you rarely have the due date and time at the prefilled time. Actually I almost always use the pre-filled time and just pick the date, at least initially. And it's actually four clicks because you have to use the date picker (two clicks) and then pick the hour and the minute. I can see resetting the date being annoying though, but that's a generic problem of all date and time fields. Maybe we should add some kind of "reset button" to these fields? No, it was solved perfectly by having a "No due date" radio button.

05/25/2007 02:56:55 PM	Jan Schneider	Comment #5	Reply to this comment
I can set due dates again now, but only if I explicitly pick the hour and minute. This was due to your changes in Horde_Form, see my reply on dev@. I'd like to get the old due date interface back, though - it's a pain to have three clicks to get the date + time, and to have 5 clicks to go back to not having a due date. We can put it in a custom renderer like the alarms. It's two clicks if you use the date picker. And it wasn't really less clicks in the old widget, because you rarely have the due date and time at the prefilled time. I can see resetting the date being annoying though, but that's a generic problem of all date and time fields. Maybe we should add some kind of "reset button" to these fields?

05/25/2007 05:08:16 AM	Chuck Hagenbuch	Comment #4	Reply to this comment
I can set due dates again now, but only if I explicitly pick the hour and minute. I'd like to get the old due date interface back, though - it's a pain to have three clicks to get the date + time, and to have 5 clicks to go back to not having a due date. We can put it in a custom renderer like the alarms.

05/23/2007 06:20:04 PM	Chuck Hagenbuch	Comment #3	Reply to this comment
I don't see the alarm problem anymore, but due dates aren't set on new tasks still. However I haven't tracked all of the latest changes yet because of wanting to do local testing before pushing them to my family, so let me do that before worrying about this more.

05/23/2007 02:42:12 PM	Jan Schneider	Comment #2 State ⇒ Feedback	Reply to this comment
I can't reproduce this. Maybe I fixed it along the way with the rewrite. Can you try again?

05/19/2007 04:00:11 AM	Chuck Hagenbuch	Comment #1 Priority ⇒ 2. Medium State ⇒ Assigned Assigned to Jan Schneider Queue ⇒ Nag Summary ⇒ New Nag task form has problems with alarms and due dates Type ⇒ Bug	Reply to this comment
When I create a new task after the task form moved to Horde_Form, I can't set the due date successfully, and even though I didn't set an alarm, an alarm is created with an alarm_start of 1969-12-31 18:59:00 (which then can't be removed, as far as I can tell, except by deleting it directly from the database).