6.0.0-beta1
7/25/25

[#4763] Due date not working correctly
Summary Due date not working correctly
Queue Whups
Type Bug
State Resolved
Priority 2. Medium
Owners chuck (at) horde (dot) org
Requester kmekc (at) web (dot) de
Created 12/12/2006 (6800 days ago)
Due
Updated 01/18/2007 (6763 days ago)
Assigned 01/18/2007 (6763 days ago)
Resolved 01/18/2007 (6763 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
01/18/2007 10:11:57 PM php (at) ideacode (dot) com Comment #6 Reply to this comment
This is a different problem, not what was originally reported; in the
future, please create a new ticket for different problems (updating
an existing ticket for the same problem is fine, and yes, sometimes
it's hard to know which is which).
Yeah, the original description of the problem was vague enough that I 
repurposed the ticket; sorry about that, but glad it's addressed.  (We 
have a ticket explosion here, so I look to keep the numbers down as 
much as possible.)
01/18/2007 03:50:34 AM Chuck Hagenbuch Comment #5
State ⇒ Resolved
Reply to this comment
Fixed in CVS.
01/18/2007 03:46:05 AM Chuck Hagenbuch Comment #4
Assigned to Chuck Hagenbuch
State ⇒ Assigned
Reply to this comment
This is a different problem, not what was originally reported; in the 
future, please create a new ticket for different problems (updating an 
existing ticket for the same problem is fine, and yes, sometimes it's 
hard to know which is which).
01/15/2007 02:17:21 PM php (at) ideacode (dot) com Comment #3 Reply to this comment
You need a newer Horde version.
Running PHP 5.1.4, Horde 3.1.1, and Whups 1.0-cvs, we experienced a 
similar problem during the 2006-2007 transition.  Here's the scenario:



1. Ticket created during 2006, with due date set to date in 2006 (eg 
29 Dec 2006)

2. Click Update to change ticket information (eg state from Implement 
to Stalled)

3. Click Save



Ticket will not save because the year drop down no longer contains 
2006.  Any ticket that is updated in a year different than the one in 
which it's created will have this problem.  Updating the due date is 
not desired because we want to keep the fact that it's past due (hence 
the stalled state).



This is a general problem with selects populated from a fixed list.   
One solution is to populate the select with the correct values, then 
if the current value is not in the list, add it also.



We hacked Horde to include 2006 regardless, but this will have the 
same problem next year.  I'm not sure if newer versions of Horde have 
addressed this, but thought I would post if not.
12/12/2006 10:09:42 AM Jan Schneider Comment #2
State ⇒ Not A Bug
Reply to this comment
You need a newer Horde version.
12/12/2006 09:26:13 AM kmekc (at) web (dot) de Comment #1
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Due date not working correctly
Queue ⇒ Whups
State ⇒ Unconfirmed
Reply to this comment
At my whups installation i can't add a new ticket, because the the 
year tab for the due date is not showing. I just have a empty drop down.



Reinstall of whups doesn't helped. Using Horde 3.1.3 and whups version 
from 12.12.2006

Saved Queries