See the thread starting with:
http://lists.bestpractical.com/pipermail/rt-users/2006-July/040503.html
On 7/20/06, Mathew Snyder <[EMAIL PROTECTED]> wrote:
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?
Thanks,
Mathew Snyder
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]
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
--
Cristobal M. Palmer
UNC-CH SILS Student
TriLUG Vice Chair
[EMAIL PROTECTED]
[EMAIL PROTECTED]
ils.unc.edu/~cmpalmer
"Television-free since 2003"
<tarheelcoxn> iank has trouble with English. his native language is Python
<iank> Yeah
<iank> I'm forced
<iank> To indent
<iank> My sentences
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]
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
