[rt-users] Searching merged tickets yields missing results

[Ben Goodwin]

For now, I've commented out the following code in
lib/RT/Tickets_Overlay_SQL.pm

  # We only want to look at EffectiveId's (mostly) for these searches.
  unless (exists $self->{_sql_looking_at}{'effectiveid'}) {
  $self->SUPER::Limit( FIELD           => 'EffectiveId',
                     ENTRYAGGREGATOR => 'AND',
                     OPERATOR        => '=',
                     QUOTEVALUE      => 0,
                     VALUE           => 'main.id'
    );    #TODO, we shouldn't be hard #coding the tablename to main.
    }

I realize two problems this will create, which I can live with for now
(recalling tickets 1269 and 1270, 1269 contains 'testcandidate1' and 1270
contains 'testcandidate2' and 1270 was merged into 1269)
1) Searching for 'testcandidate2' will result in link to ticket 1270 instead
of 1269
2) Search results will contain duplicate ticket numbers (well, they'll show
as different numbers, but they point at the same effective ticket) if a
match is found across multiple tickets that are now merged

I'm not sure of the proper way to solve this problem.

    -=| Ben

----- Original Message ----- 
From: "Ben Goodwin" <ben at atomicmatrix.net>
To: <rt-users at lists.bestpractical.com>
Sent: Thursday, January 01, 2004 8:46 PM
Subject: Re: [rt-users] Searching merged tickets yields missing results


> > Merged tickets should never show up in search results, only the tickets
> > that they were merged into. does 1269 not have its id == its
> > EffectiveId?
>
> The contents should cause a search match and result in the 'real' ticket
> number being displayed, but it doesn't; 1269 should show up in the list of
> tickets when I perform my search.  1269's EID is 1269, and 1270's is 1269.
>
>     -=| Ben
>