[rt-devel] Problem with custom field searching in RT 3.0.2pre4

[Robert Spier]

--- lib/RT/Tickets_Overlay.pm   10 Mar 2003 03:01:17 -0000      1.35
+++ lib/RT/Tickets_Overlay.pm   1 May 2003 23:12:53 -0000
@@ -147,7 +147,7 @@
                                     'NOT LIKE' => 'AND'
                                   },
 
-                 CUSTOMFIELD   => 'OR',
+                 CUSTOMFIELD   => 'AND',
                 );
 
 
In theory, the above patch does what we've discussed.

Jesse Vincent wrote:
> 
> Now that I actually understand the issue, I agree with everyon else.
> they should be anded, not ORed. 
> 
> I expect to have net access tomorrow (rather than a borrowed PC) and
> hope to spend time applying patches and rolling another pre+release. If
> I'm really lucky, I may eve nget 3.0.2 out the door.
> 
> 	-j
> 
> 
> 
> On Thu, May 01, 2003 at 10:53:21AM +0200, Paul Wagland wrote:
> > Hi all,
> > 
> > Sorry for not jumping yesterday... we had a public holiday here. :-)
> > 
> > Anyway, yes, the issue that I was reporting is that if I have two different
> > custom fields then it does an or. I agree that if I have one custom field it
> > _should_ be an or.
> > 
> > So, to give an example:
> > 
> > I have a custom field "a" (CF.a) and "b" (CF.b).
> > 
> > I want to select all tickets where CF.a = "searcha" *AND* where CF.b =
> > "searchb". There is no way to do that. With every other field on the search
> > screen this is what happens.
> > 
> > To put it another way: Currently, when selecting a new field it restricts
> > your search criteria. _Unless_ you happen to of chosen a custom field, *and*
> > you already have a custom field in your search criteria.
> > 
> > So: I go to the search screen, and select queue="queuea". It returns 20
> > tickets.
> > I select another criteria, owner="pwagland". It returns 10 tickets.
> > I select another criteria, CF.a="searcha". It returns 5 tickets.
> > I select another criteria, CF.b="searchb". It returns 7 tickets!
> > 
> > This last bit is inconsistent, and confusing.
> > 
> > I accept (and expect for that matter) that if the last line had of been
> > CF.a="searcha2" it would return more tickets, but I am trying to *restrict*
> > the search, and it actually broadens it.
> > 
> > That is the bug that I was reporting :-)
> > 
> > Cheers,
> > Paul
> > 
> > > -----Original Message-----
> > > From: rt-devel-admin at lists.fsck.com
> > > [mailto:rt-devel-admin at lists.fsck.com]On Behalf Of Autrijus Tang
> > > Sent: Wednesday, April 30, 2003 14:43
> > > To: Robert Spier
> > > Cc: Jesse Vincent; Autrijus Tang; Paul Wagland; Rt-Devel at Lists. Fsck. Com
> > > Subject: Re: [rt-devel] Problem with custom field searching in RT
> > > 3.0.2pre4
> > >
> > >
> > > On Tue, Apr 29, 2003 at 04:04:31PM -0700, Robert Spier wrote:
> > > > Right, but the issue Paul reported is:
> > > > CF1 OR CF2
> > > > As opposed to CF1.Val1 OR CF1.Val2
> > >
> > > That was my interpretation too, and I still think that AND makes
> > > most sense.
> > >
> > > /Autrijus/
> > > _______________________________________________
> > > rt-devel mailing list
> > > rt-devel at lists.fsck.com
> > > http://lists.fsck.com/mailman/listinfo/rt-devel
> > >
> > >
> > 
> > 
> > _______________________________________________
> > rt-devel mailing list
> > rt-devel at lists.fsck.com
> > http://lists.fsck.com/mailman/listinfo/rt-devel
> http://www.bestpractical.com/rt  -- Trouble Ticketing. Free.