On Thu, Sep 05, 2013 at 08:10:37AM +1000, Sam Wilson wrote: > Turns out this was a pebkac issue for me. We had set a SubjectTag for each > queue rather than > using the sitename. After removing the individual subjecttags this is > working correctly.
Subject Tags, set on the Queue Admin page, work fine for the scenario you describe, we use them in production today with tickets that move across Queues and are sent to old email addresses. RT looks for the $rtname, $EmailSubjectTagRegex and every queue subject tag configured in the system I expect you have a misconfiguration or custom local development. -kevin > On Thu, Sep 5, 2013 at 5:19 AM, Kevin Falcone > <[1]falc...@bestpractical.com> wrote: > > On Wed, Sep 04, 2013 at 12:53:29PM +1000, Sam Wilson wrote: > > Hi rt-users, > > I have configured a multiple queue RT instance with mailgate as > follows, we create new > tickets > > in the support queue before moving them to specific queues to be > worked on and closed. > > [2]supp...@example.com > > [3]que...@example.com > > [4]que...@example.com > > By itself mailgate is working fine. For example I can raise a ticket > directly in queue1 > via > > email. > > The issue is around the process of creating all tickets in the support > pool before moving > to a > > different queue. This means that users who reply to > [5]supp...@example.com after having > the > > ticket moved will actually duplicate a new ticket with a new ID as > their original ticket > is > > now at [6]que...@example.com. > > This isn't how a properly configured RT works. > Are your users removing the Subject Tag? > > The [sitename #1234] in your email subjects allow RT to route email > sent to [7]supp...@example.com back to the ticket which has been moved to > queue2.
pgpRBtWKUAH6e.pgp
Description: PGP signature
