Thu, 09 Apr 2026 21:18:37 +0000 https://bugs.horde.org/ticket/4101 Create updateTicket API method This patch creates an updateTicket API method which is very similar to the Update form in the Whups Web GUI. This bug depends on bug #4100 as it references the EditTicket form. Sat, 01 Jul 2006 05:30:05 +0000 https://bugs.horde.org/ticket/4101#t21556 Committed, thanks! Mon, 03 Jul 2006 02:35:02 +0000 https://bugs.horde.org/ticket/4101#t21596 After updating whups (and everything else) I got a problem. Commenting on tickets is still possible, but updating the state of a ticket is not working anymore. Ticktes remain e.g. "assigned" instead of being "resolved". Volker Fri, 07 Jul 2006 14:49:47 +0000 https://bugs.horde.org/ticket/4101#t21782 I can't recreate this issue. There is one related issue and that is when the EditForm was moved out into its own file the form name was lost so every attempt to submit updated on a ticket would simply refresh the page. However this would prevent *any* updates to a ticket, not just the State. Once I corrected that problem I was able to update the State and every other field of the ticket. Is there a reason you believe your problem with the State field is related to this ticket? This ticket only created an API call and didn't touch any of Whups' internals so it seems highly unlikely to me that they would be related. Sat, 08 Jul 2006 15:12:20 +0000 https://bugs.horde.org/ticket/4101#t21827 > Is there a reason you believe your problem with the State field is > related to this ticket? This ticket only created an API call and > didn't touch any of Whups' internals so it seems highly unlikely to > me that they would be related. I can't tell exactly, but at least, your patch to bug 4101 resolved the problem, I had. Sun, 09 Jul 2006 15:14:27 +0000 https://bugs.horde.org/ticket/4101#t21855 Sorry, it was the patch attached to bug 4000 I wanted to refer to. Sun, 09 Jul 2006 15:17:59 +0000 https://bugs.horde.org/ticket/4101#t21856 I didn't open bug #4000 or attach a patch to it. Perhaps you mean bug #4100? Regardless it sounds like the issue is resolved for you. Sun, 09 Jul 2006 18:16:29 +0000 https://bugs.horde.org/ticket/4101#t21862