To all,

I concur, but not only that, a scrip should be created to notify the original Requestor on a merge as well as the owner or whomever is administrating the Queue could add the requestor name from the old ticket (#100) to the ticket merged into (#200) by updating "people" of ticket #200. That way the requestor of ticket #100 will always get the communication you have set up a requestor to get. Now, if RT is not showing you #200 when you search for #100, that is a bug, but that does not remove the need for good admin scrips and communication on merges.

Kenn
LBNL

Drew Barnes wrote:
This is when an OnMerge scrip could be useful. Merge the ticket, notify the source ticket's owner of their new ticket number, problem solved.

Sven Sternberger wrote:
On Tue, 2006-07-18 at 10:56 -0400, Jesse Vincent wrote:
the merge function in rt3.6 seems to be broken, after merge I can't find the ticket-id of the merged ticket,
Of either ticket or the ticket you merged into another one?
only the ticket which is merged (source)

Merged tickets should entirely cease to have their own identities.

but if I send a reply to a customer and afterwards I merge this ticket.
What happens when the customer calls me and give me his ticket id? I
have no chance to find his ticket.

I can't find the subject,
I can't find the content

I think this is valuable information which should be searchable.

sven


_______________________________________________
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

_______________________________________________
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

Reply via email to