Hi,
In my current setup, I have created two states for a ticket named
"Resolved" type "Closed" and
"Re-Opened" type "Open"
A ticket with state "Resolved" is set to next state as "Re-Opened" when customer add a followup. However, when agent tries to post a reply to "Re-Opened" ticket and set the next state as "Resolved", we receive an error while submitting for the field
Pending Date (for pending* states): "Invalid Date (need a future date!).
The auto populated date is 24 hours ahead of current date as shown below
When agent clicks on calander and select the same date without making any chanes to time etc, the changes to the ticket are submitted.
While searching, I found the following viewtopic.php?f=62&t=7230, but I think this is not what I need.
I am wondering, why the ticket is not submitted with default auto populated date for pending date (even the state is not pending) and why it gets submitted only after pulling up the calander without any changes?
How can I correct this behaviour?
Any help is much appreciated.
[SOLVED] Pending Date (for pending* states): Invalid Date
Moderator: crythias
[SOLVED] Pending Date (for pending* states): Invalid Date
You do not have the required permissions to view the files attached to this post.
Last edited by ashley420 on 17 Jan 2013, 17:51, edited 1 time in total.
OTRS 3.3.3 on Linux (CentOS 6.5 x64) with MySQL database. Customer and Agent backend Microsoft AD on Windows 2003.
Re: Pending Date (for pending* states): Invalid Date
On close watching the error, I figured that a +1 was added to the auto populated date. One of the other OTRS admin changed the settings in Framework -> Core::Time TimeZone to +1 from Default value: + 0. Changing this to default value fixed the problem.
Sorry about that.
Sorry about that.
OTRS 3.3.3 on Linux (CentOS 6.5 x64) with MySQL database. Customer and Agent backend Microsoft AD on Windows 2003.