> (from Jerrad)
> It's not exactly the same, but what about where Last Updated > Told?
This looks like it would have done what I want, but "Advanced" screen
of QueryBuilder won't accept it. Upon "Apply," I get the error:
"Wrong query, expecting a VALUE in 'LastUpdated > >Told<--here'"
> (from Ruslan)
> Try LastUpdatedBy.EmailAddress not like '@...'.
In version 3.8.4, QueryBuilder accepts this input, but it has no
effect on the search results. The search seems to execute but ignore
this clause. It does throw an error in the log for "sub _EnumLimit":
[error]: Invalid Operation: LIKE for LastUpdatedBy at
/usr/share/request-tracker3.8/lib/RT/Tickets_Overlay.pm line 339.
> (from Raed)
> when we are waiting on a customer response we set a ticket status to stalled
Thanks for this, but I think we want to reserve the stalled status for
more atypical conditions that delay a ticket as opposed to normal
delay between correspondence. I see how you do use it though to find
the items where the ball is or is not in your court.
Any other ideas on how to employ the EmailAddress of the LastUpdatedBy
person, or how to compare LastUpdated to Told (QueryBuilder seems to
want a literal value for the comparison)?
Allen
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: sa...@bestpractical.com
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
