(resend email, sorry if sent 2 times)
I, I’ve tried the fix but it doesn’t seem to be related to _CustomFieldLimit
in $RTPATH/lib/RT/Tickets_Overlay.pm.
It doesn’t solve this problem: this should return 1 result and return 0
‘CF.{TicketType}’ = ‘Feature Request’ AND Queue = ‘General’ AND
‘CF.{TicketState}’ = ‘FAQ Review’
but this one: return 2 results
‘CF.{TicketType}’ = ‘Feature Request’ AND Queue = ‘General’
Is it really supposed to help for search results and why?
Or any other ideas?
PatrickFrom: Todd Chapman [mailto:todd@chaka.net]
Sent: Wednesday, April 13, 2005 8:09 AM
To: Patrick Rousseau-Mathieu
Cc: rt-devel@bestpractical.com
Subject: Re: [Rt-devel] Custom Field search bug in 3.4 HEAD
I think this will fix your problem.
http://rt3.fsck.com/Ticket/Display.html?id=6559
I, I’m trying to fix this bug and I’ve got a problem.
the problem is that I need to know the number of customField selected in a
search to used it in the function _CustomFieldLimit in the file
$RTPATH/local/lib/RT/Tickets_Overlay.pm. So then I can do a loop to and
some
JOIN and WHERE clause in the query.
But I can’t find where and witch function is calling _CustomFieldLimit. So
if i found the calling function, I can just pass some more argument to
_CustomFieldLimit to know how many customField there is in the query and
then the query should be working fine.
any idea?
Thanks.
Patrick
-----Original Message-----
From: rt-devel-bounces@lists.bestpractical.com
[mailto:rt-devel-bounces@lists.bestpractical.com]On Behalf Of Todd
Chapman
Sent: Tuesday, March 22, 2005 2:42 PM
To: rt-devel@bestpractical.com
Subject: [Rt-devel] Custom Field search bug in 3.4 HEAD
Try these searches at rt3.fsck.com with format:
’ id/TITLE:#',
‘Subject/TITLE:Subject’,
‘Status’,
‘QueueName’,
‘OwnerName’,
‘Priority’,
‘NEWLINE’,
‘’,
‘Requestors’,
‘CreatedRelative’,
‘ToldRelative’,
‘LastUpdatedRelative’,
‘TimeLeft’,
‘CustomField.{Found In}’,
‘CustomField.{Fix In}’
Search 1:
Queue = ‘RTIR’ AND ‘CF.{Found In}’ = ‘1.0’
(2 tickets found)
Search 2:
Queue = ‘RTIR’ AND ‘CF.{Found In}’ = ‘1.0’ AND ‘CF.{Fix In}’ = ‘1.2.0
release’
(0 tickets found - should be 1)
-Todd
Rt-devel mailing list
Rt-devel@lists.bestpractical.com
The rt-devel Archives