Charts broken when searching on 'Updated'

RT Users
1

Hi,

With RT 4 I am unable to build charts from searches that use the Updated field. For example:
Queue = ‘support’ AND Updated > ‘2 weeks ago’

This search finds 89 tickets. However, the “Chart” link on the results page brings up a blank chart and the message “No tickets found.” Clicking “Show Results” on this page does find 89 tickets again, so the search itself seems to work properly.

Charts work fine for other searches; in fact if I modify the query to use Created instead of Updated, everything is fine.

This is with RT 4.0.1. I don’t remember if 4.0.0 also had this problem or not, but 4.0.1rc1 definitely did. I think this worked properly with 3.8, but I don’t have a 3.8 instance around any more to verify that.

Also, nothing gets logged indicating any problem. Even with LogToFile debug, the only thing logged is:
[Fri Jun 24 20:16:56 2011] [debug]: RT::Date used Time::ParseDate to make ‘2 weeks ago’ 1307737016 (/opt/rt4/sbin/…/lib/RT/Date.pm:222)

Any ideas?

Thanks,

Andrew Daugherity
Systems Analyst
Division of Research, Texas A&M University

2

Hi,

You can file a bug report. However, LastUpdated in the query will
solve it for you and would actually be faster than Updated.On Sat, Jun 25, 2011 at 12:39 AM, Daugherity, Andrew W adaugherity@tamu.edu wrote:

Hi,

With RT 4 I am unable to build charts from searches that use the Updated field. For example:
Queue = ‘support’ AND Updated > ‘2 weeks ago’

This search finds 89 tickets. However, the “Chart” link on the results page brings up a blank chart and the message “No tickets found.” Clicking “Show Results” on this page does find 89 tickets again, so the search itself seems to work properly.

Charts work fine for other searches; in fact if I modify the query to use Created instead of Updated, everything is fine.

This is with RT 4.0.1. I don’t remember if 4.0.0 also had this problem or not, but 4.0.1rc1 definitely did. I think this worked properly with 3.8, but I don’t have a 3.8 instance around any more to verify that.

Also, nothing gets logged indicating any problem. Even with LogToFile debug, the only thing logged is:
[Fri Jun 24 20:16:56 2011] [debug]: RT::Date used Time::ParseDate to make ‘2 weeks ago’ 1307737016 (/opt/rt4/sbin/…/lib/RT/Date.pm:222)

Any ideas?

Thanks,

Andrew Daugherity
Systems Analyst
Division of Research, Texas A&M University

2011 Training: http://bestpractical.com/services/training.html

Best regards, Ruslan.

3

Hi,

You can file a bug report. However, LastUpdated in the query will
solve it for you and would actually be faster than Updated.

It does indeed work (and runs faster too), thanks!

What exactly is the difference between Updated and LastUpdated? Is there any reason to have both presented in the search builder UI when LastUpdated clearly works better (and from what I can tell, both return the same results)?

-Andrew

4

Hi,

You can file a bug report. However, LastUpdated in the query will
solve it for you and would actually be faster than Updated.

It does indeed work (and runs faster too), thanks!

What exactly is the difference between Updated and LastUpdated? Is there any reason to have both presented in the search builder UI when LastUpdated clearly works better (and from what I can tell, both return the same results)?

They are really different. Updated = ‘2010-03-25’ means “tickets that
has at least one transaction on the date”. “Updated” makes less sense
in comparisions as it can be effectively replaced by Created or
LastUpdated.

-Andrew

Best regards, Ruslan.