LastUpdated x days ago

I’m trying to write a script that will check for tickets last updated
15 days ago. I’m using the FromSQL method. As far as I can tell, it
doesn’t like the ‘-15 days’ or ‘15 days ago’ options. If I use either
one every ticket in the queue I’m searching in is returned. Am I
doomed to perform a separate comparison for tickets last updated
1296000000 miliseconds ago or is there a more succinct way to do this?

-Mathew

Matthew;

I 've used:
LastUpdated = ‘15 days ago’

And it always worked for me.

Regards;
Roy

Matthew,

We use "LastUpdated > ‘15 days ago’ and it works fine. Every ticket updated
15 or more days ago gets in the report. Are there other criteria you forgot
to mention?

Kenn
LBNLOn Mon, Oct 11, 2010 at 2:27 AM, Raed El-Hames Raed.El-Hames@vialtus.comwrote:

Matthew;

I 've used:
LastUpdated = ‘15 days ago’

And it always worked for me.

Regards;
Roy

-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-
bounces@lists.bestpractical.com] On Behalf Of Mathew Snyder
Sent: 11 October 2010 03:23
To: RT Users
Subject: [rt-users] LastUpdated x days ago

I’m trying to write a script that will check for tickets last updated
15 days ago. I’m using the FromSQL method. As far as I can tell, it
doesn’t like the ‘-15 days’ or ‘15 days ago’ options. If I use either
one every ticket in the queue I’m searching in is returned. Am I
doomed to perform a separate comparison for tickets last updated
1296000000 miliseconds ago or is there a more succinct way to do this?

-Mathew

RT Training in Washington DC, USA on Oct 25 & 26 2010
Last one this year – Learn how to get the most out of RT!

RT Training in Washington DC, USA on Oct 25 & 26 2010
Last one this year – Learn how to get the most out of RT!

Matthew,

Opps. Acutally that’s LastUpdated > ‘14 days ago’.

Kenn
LBNLOn Mon, Oct 11, 2010 at 9:48 AM, Kenneth Crocker kfcrocker@lbl.gov wrote:

Matthew,

We use "LastUpdated > ‘15 days ago’ and it works fine. Every ticket updated
15 or more days ago gets in the report. Are there other criteria you forgot
to mention?

Kenn
LBNL

On Mon, Oct 11, 2010 at 2:27 AM, Raed El-Hames Raed.El-Hames@vialtus.comwrote:

Matthew;

I 've used:
LastUpdated = ‘15 days ago’

And it always worked for me.

Regards;
Roy

-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-
bounces@lists.bestpractical.com] On Behalf Of Mathew Snyder
Sent: 11 October 2010 03:23
To: RT Users
Subject: [rt-users] LastUpdated x days ago

I’m trying to write a script that will check for tickets last updated
15 days ago. I’m using the FromSQL method. As far as I can tell, it
doesn’t like the ‘-15 days’ or ‘15 days ago’ options. If I use either
one every ticket in the queue I’m searching in is returned. Am I
doomed to perform a separate comparison for tickets last updated
1296000000 miliseconds ago or is there a more succinct way to do this?

-Mathew

RT Training in Washington DC, USA on Oct 25 & 26 2010
Last one this year – Learn how to get the most out of RT!

RT Training in Washington DC, USA on Oct 25 & 26 2010
Last one this year – Learn how to get the most out of RT!

Hi.

LastUpdated > x means updated since x. < means updated before x. So
LastUpdated < ‘15 days ago’ is probably what you need and means tickets that
are not touched last 15 days.

Regards, Ruslan. From phone.

Matthew,

Opps. Acutally that’s LastUpdated > ‘14 days ago’.

Kenn
LBNL

Matthew,

We use "LastUpdated > ‘15 days ago’ and it works fine. Every ticket
updated
15 or more days ago gets in the report. Are there other criteria you
forgot

Is it possible to use other units besides “days”?

The searching uses Time::ParseDate, so this may help Time::ParseDate - date parsing both relative and absolute - metacpan.org

The system is not interpreting the ‘15 days ago’ parameter as expected. Instead of filtering tickets based on this relative time frame, the search results include all tickets, disregarding the specified time condition. I’ve scoured the documentation and community forums to find a more concise solution, but it appears that I might need to resort to a workaround by converting the time duration to seconds and performing a separate comparison.