[rt-users] Search on merged ticket differs between 3.4.5 & 3.6.0

Kenneth Crocker KFCrocker at lbl.gov
Mon Jul 17 18:27:32 EDT 2006


	Not to say 3.6.0 is perfect, but we like the current design as far as 
merged tickets. If we have merged the two (using your example of #100 
and #200), then #100 really should never be looked at anyway, other than 
what was originally appended to #200. We really don't want anyone 
looking at #100 anymore, ever. It is old, has been merged into another 
ticket and, therefore, is not relevent to any further research or 
discussion among anyone in our organization and we never want it 
referred to either. We want everyone to refer to the ticket that is 
active and being worked on.  We feel that is consistent with the 
decision to merge them in the first place. Anything else could get 
confusing, like one person referring to #100 while another is referring 
to #200 in an E_mail conversation. It opens the door to miscommunication 
and communication is hard enough without opening the door to confusion. 
But hey, that's just our opinion and how we like it. Everyone has there 


Barry L. Kline wrote:
> We recently upgraded our RT instance from 3.4.5 to 3.6.0.   The new
> version is really great and I like the fact that the front page can now
> be customized so very easily.
> There is one thing that has changed, and that's the behaviour of RT when
> dealing with merged tickets.   Let's say I have two tickets:  100 & 200.
>    I merge 100 into 200.  In 3.4.5 I could type either ticket number
> into the search box and bring up ticket 200.  In 3.6.0 I can only access
> ticket 200.  Trying 100 in the search box returns "0 tickets found".
> If I use rt-mailgate and send an e-mail with a subject of [mydomain.com
> #100] the transaction is properly appended to ticket 200, so there is no
> problem along those lines.
> Is this "working as designed" or has something gone awry between the two
> versions?
> Barry
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
> Buy a copy at http://rtbook.bestpractical.com
> We're hiring! Come hack Perl for Best Practical: http://bestpractical.com/about/jobs.html

More information about the rt-users mailing list