Fri, 10 Apr 2026 09:50:19 +0000 https://bugs.horde.org/ticket/4763 Due date not working correctly 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 Tue, 12 Dec 2006 09:26:13 +0000 https://bugs.horde.org/ticket/4763#t27300 You need a newer Horde version. Tue, 12 Dec 2006 10:09:42 +0000 https://bugs.horde.org/ticket/4763#t27306 > 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. Mon, 15 Jan 2007 14:17:21 +0000 https://bugs.horde.org/ticket/4763#t28506 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). Thu, 18 Jan 2007 03:46:05 +0000 https://bugs.horde.org/ticket/4763#t28651 Fixed in CVS. Thu, 18 Jan 2007 03:50:34 +0000 https://bugs.horde.org/ticket/4763#t28654 > 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.) Thu, 18 Jan 2007 22:11:57 +0000 https://bugs.horde.org/ticket/4763#t28677