Problem with Reminders Due date

To list,

I’m on 3.8.7 and just noticed that when I select a due date for a reminder
(either entering directly or using the “calendar”) it always ends up as
30-Nov-1999.
I also noticed that when I resolve the ticket, the reminder stays open.
Has anyone else noticed this? Does anyone have a fix or have I set something
wrong?
Thanks.

Kenn
LBNL

I’m on 3.8.7 and just noticed that when I select a due date for a reminder (either entering
directly or using the “calendar”) it always ends up as 30-Nov-1999.

This sounds like a local bug, I can’t replicate it against vanilla 3.8.7

I also noticed that when I resolve the ticket, the reminder stays open.
Has anyone else noticed this? Does anyone have a fix or have I set something wrong?
Thanks.

I’m not aware of any code in RT to go resolve Reminders after a ticket
is resolved. It could certainly be done with a Scrip

-kevin

Kevin,

OH. I’d heard that it* did* resolve the reminders, but no problema. I’ll get
to work on the scrip. Shouldn’t be too difficult. Thanks. As to the local
bug thing, I’m not sure where to look on that. The configuration seems to
work well on everything else.

Kenn
LBNLOn Tue, Mar 23, 2010 at 6:52 AM, Kevin Falcone falcone@bestpractical.comwrote:

On Thu, Mar 11, 2010 at 03:43:37PM -0800, Kenneth Crocker wrote:

I’m on 3.8.7 and just noticed that when I select a due date for a
reminder (either entering
directly or using the “calendar”) it always ends up as 30-Nov-1999.

This sounds like a local bug, I can’t replicate it against vanilla 3.8.7

I also noticed that when I resolve the ticket, the reminder stays
open.
Has anyone else noticed this? Does anyone have a fix or have I set
something wrong?
Thanks.

I’m not aware of any code in RT to go resolve Reminders after a ticket
is resolved. It could certainly be done with a Scrip

-kevin

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Kevin,

As to the date ending up as November 1999, I looked at the TRANSACTION Table
and this is what I saw:

Id Type Field Old Value New
Value
77793 Set Due 2010-03-26 07:00:00 1999-11-30 08:00:00

Creator Created ObjectType
1 24-Mar-2010 22:53:04 RT::Ticket

It looks like the old and new values got swapped around and I can’t figure
what local bug or setting or configuration would do this to the Transaction
record.

Any ideas?

Thanks.

Kenn
LBNLOn Tue, Mar 23, 2010 at 6:52 AM, Kevin Falcone falcone@bestpractical.comwrote:

On Thu, Mar 11, 2010 at 03:43:37PM -0800, Kenneth Crocker wrote:

I’m on 3.8.7 and just noticed that when I select a due date for a
reminder (either entering
directly or using the “calendar”) it always ends up as 30-Nov-1999.

This sounds like a local bug, I can’t replicate it against vanilla 3.8.7

I also noticed that when I resolve the ticket, the reminder stays
open.
Has anyone else noticed this? Does anyone have a fix or have I set
something wrong?
Thanks.

I’m not aware of any code in RT to go resolve Reminders after a ticket
is resolved. It could certainly be done with a Scrip

-kevin

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Kevin,

As to the date ending up as November 1999, I looked at the TRANSACTION Table and this is what
I saw:

Without seeing the other transactions, this is just a guess, but that
change is by 1 (RT::System) so I would suspect a scrip

-kevin

Kevin,

GEZZ! I’m an idiot. I found a scrip that took the date from a CF and
modified it for Due date. Trouble was, I didn’t check to see if the date or
CF existed for that transaction. DUH!!

Kenn
LBNLOn Thu, Mar 25, 2010 at 7:20 AM, Kevin Falcone falcone@bestpractical.comwrote:

On Wed, Mar 24, 2010 at 04:10:50PM -0700, Kenneth Crocker wrote:

Kevin,

As to the date ending up as November 1999, I looked at the TRANSACTION
Table and this is what
I saw:

Without seeing the other transactions, this is just a guess, but that
change is by 1 (RT::System) so I would suspect a scrip

-kevin

Link: [1]File-List
Id Type Field Old Value New Value
77793 Set Due 2010-03-26 07:00:00 1999-11-30 08:00:00

Creator Created ObjectType
1 24-Mar-2010 22:53:04 RT::Ticket

It looks like the old and new values got swapped around and I can’t
figure what local bug or
setting or configuration would do this to the Transaction record.

Any ideas?

Thanks.

Kenn
LBNL

On Tue, Mar 23, 2010 at 6:52 AM, Kevin Falcone <[2] falcone@bestpractical.com> wrote:

 On Thu, Mar 11, 2010 at 03:43:37PM -0800, Kenneth Crocker wrote:
 > I'm on 3.8.7 and just noticed that when I select a due date for a

reminder (either

 entering
 > directly or using the "calendar") it always ends up as

30-Nov-1999.

 This sounds like a local bug, I can't replicate it against vanilla

3.8.7

 > I also noticed that when I resolve the ticket, the reminder stays

open.

 > Has anyone else noticed this? Does anyone have a fix or have I set

something wrong?

 > Thanks.

 I'm not aware of any code in RT to go resolve Reminders after a

ticket

 is resolved. It could certainly be done with a Scrip
 -kevin

 Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
 Buy a copy at [3]http://rtbook.bestpractical.com

References

Visible links
1.
file:///C:%5CDOCUME%7E1%5CKFCROC%7E1%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C01%5Cclip_filelist.xml
2. mailto:falcone@bestpractical.com
3. http://rtbook.bestpractical.com/

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Kevin,

Yep. That was it. Thanks.

Kenn
LBNLOn Thu, Mar 25, 2010 at 9:23 AM, Kenneth Crocker kfcrocker@lbl.gov wrote:

Kevin,

GEZZ! I’m an idiot. I found a scrip that took the date from a CF and
modified it for Due date. Trouble was, I didn’t check to see if the date or
CF existed for that transaction. DUH!!

Kenn
LBNL

On Thu, Mar 25, 2010 at 7:20 AM, Kevin Falcone falcone@bestpractical.comwrote:

On Wed, Mar 24, 2010 at 04:10:50PM -0700, Kenneth Crocker wrote:

Kevin,

As to the date ending up as November 1999, I looked at the
TRANSACTION Table and this is what
I saw:

Without seeing the other transactions, this is just a guess, but that
change is by 1 (RT::System) so I would suspect a scrip

-kevin

Link: [1]File-List
Id Type Field Old Value New Value
77793 Set Due 2010-03-26 07:00:00 1999-11-30 08:00:00

Creator Created ObjectType
1 24-Mar-2010 22:53:04 RT::Ticket

It looks like the old and new values got swapped around and I can’t
figure what local bug or
setting or configuration would do this to the Transaction record.

Any ideas?

Thanks.

Kenn
LBNL

On Tue, Mar 23, 2010 at 6:52 AM, Kevin Falcone <[2] falcone@bestpractical.com> wrote:

 On Thu, Mar 11, 2010 at 03:43:37PM -0800, Kenneth Crocker wrote:
 > I'm on 3.8.7 and just noticed that when I select a due date for a

reminder (either

 entering
 > directly or using the "calendar") it always ends up as

30-Nov-1999.

 This sounds like a local bug, I can't replicate it against vanilla

3.8.7

 > I also noticed that when I resolve the ticket, the reminder stays

open.

 > Has anyone else noticed this? Does anyone have a fix or have I

set something wrong?

 > Thanks.

 I'm not aware of any code in RT to go resolve Reminders after a

ticket

 is resolved. It could certainly be done with a Scrip
 -kevin

 Discover RT's hidden secrets with RT Essentials from O'Reilly

Media.

 Buy a copy at [3]http://rtbook.bestpractical.com

References

Visible links
1.
file:///C:%5CDOCUME%7E1%5CKFCROC%7E1%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C01%5Cclip_filelist.xml
2. mailto:falcone@bestpractical.com
3. http://rtbook.bestpractical.com/

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com