[rt-users] Possible Bug?

[Jason A. Diegmueller]

> We've encountered an issue that we don't particularly like nor do we
> know if it is engineered or a bug.  It involves the searching of merged
> tickets and is repeatable for all merged tickets in our database.
>
> It would appear that after a merge it is impossible to find the ticket
> merged INTO another based on the merged tickets id.  To clarify:
>
> Ticket #1 comes in.
> Ticket #2 comes in and either is related to or is identical to ticket #1.
> Ticket #2 is merged into ticket #1.
> Searching for ticket #2 results in nothing instead of redirecting to
> ticket #1 giving the impression that ticket #2 does not exist.
>
> Is this a "feature"?  If so how can I make it work the way I want it to?
> Or is it just a bug?

Mathew--

This has been discussed a bit in the last week, and I think it's been 
agreed upon that it is a bug.  Refer to the following thread:

On Tue, Jul 18, 2006 at 05:48:41PM +0200, Sven Sternberger wrote:
> On Tue, 2006-07-18 at 11:27 -0400, Jesse Vincent wrote:
> > It should be the case that searching for the old ticket number will 
get
> > you the new ticket.
> >
> This is what I expected.
>
> I have an 3.6 installation from tarball. The installation is upgraded
> from 3.0.12. The search problem appears in tickets which are created
> before and after migration.
>

Ok, then yes, that sounds like a bug.
_____________________________________