Time stamp on due date woes...

mrramsey

Hi I just installed v1.6 rc5 yesterday. Great program! one small glitch I found in the date stamp. When a client emails back in response to a ticket the system auto assigns to the last respondent as it should but then appends a due date automatically of 12/31/1969. :

Is there a way to set the due date to 1 day from the receipt of the email?

hihello

Anybody know an answer to this? Im having the same problem and i notice that when leaving the "due date" field blank when creating a new ticket, the due date is 12/31/1969. So when you have an overdue limit, 48hr, the ticket immediatly gets set as overdue and stale, sending out notification emails...

masino_sinaga

Hey,

I have tested at mine, and everything seemed okay. The duedate field value is NULL in my table (not the value mentioned above), even if I edited the current ticket or created a new ticket from staff-panel. Using 1.6 RC5. :

Sincerely,

Masino Sinaga

hihello

Well i just created 3 tickets in a row and couldnt repeat the issue, however i do have 2 previous tickets with 1969 as a due date...

Ill keep testing and figure out how to repeat this bug exactly.

hihello

Ok, i found out that when you reopen a ticket from a closed state, it will always put in the 1969 due date... Seems like it should be null or x amount of days from the time you open it...

masino_sinaga

Thanks for your info.

I have re-tested to reopen the certain closed ticket, afterwards, the duedate is still NULL, and I think it should be! Why? Since I saw from the related code in the class.ticket.php file, around line 387 at the reopen function:

$sql= 'UPDATE '.TICKET_TABLE.' SET status='.db_input('open').',isanswered=0,updated=NOW(),reopened=NOW() WHERE ticket_id='.db_input($this->getId());

From that part of code, we see that there is no any code which will update the duedate field.

I just wondered whether the weird condition you guys mentioned above only happened to the certain MySQL version? :

Anyway, mine is 5.0.51b and everything seemed okay so far.

Sincerely,

Masino Sinaga

hihello

FYI, I am using MySQL 5.1.30...

Im not sure what all the parameters in the code mean, but shouldt it specifically set a null due date? That way it prevents MySQL from setting a default date, in which you think it may be doing...

masino_sinaga

... Im not sure what all the parameters in the code mean, but shouldt it specifically set a null due date? ...

That code did not set the NULL value to the duedate field at all.

That code means:

"Update the ticket table only for the record which has the ticket_id value equal with the specified ticket_id, by assigning the status field value with 'open', assigning the insanswered field value with 0, assigning the updated field value with the date of today, and then assigning the reopened field value with the date of today".

Sincerely,

Masino Sinaga