I do really like the built-in capability to create a related ticket, but
Dirk’s patchset adds a couple of things to it that have been really
valuable to us:
(1) The newly created ticket is preloaded with the contents of a
particular transaction, and
(2) You get to choose which queue the new ticket is going into.
Yeah, we’re only saving a bit of copying and pasting and a few clicks,
but streamlining a process is always nice, right?
RT’s callback capability made it pretty easy to convert Dirk’s patches
into something that looks more like a standalone extension. Once we get
through the start of classes here, I’ll package it up with some
documentation and an installer and make it available.
Senior Programmer/Analyst - Web Services
LeTourneau University-----Original Message-----
From: Jesse Vincent [mailto:email@example.com]
Sent: Sunday, August 24, 2008 7:26 PM
To: David Sitsky
Cc: Joop van de Wege; RT Users; Roedel, Mark
Subject: Re: [rt-users] Forking a ticket
On Aug 24, 2008, at 8:19 PM, David Sitsky wrote:
Joop van de Wege wrote:
Roedel, Mark wrote:
When we upgraded to 3.8.0, I reworked most of Dirk’s forking patch
into callbacks (I did keep the standalone select-queue page,
although at some point I’d like to try eliminating that as well with
some sort of ajaxy dropdown queue selector) so I wouldn’t have to
keep re-patching each upgrade. If there’s interest, I can knock
together some documentation and make my version available for
Please add me to the list as well, since I am using RT 3.8.0. Given
that this patch has been around for a long time, is there any reason
why it hasn’t been accepted into the core distribution of RT? It
seems like a modification a lot of people would benefit from…
Well, we started with the “Clone ticket” stuff we built for 3.8, but
many users were…quite vocal about how they preferred “create a new
related ticket” instead.
Of course, my ideal is to provide reasonable hooks to make it easy to
create an extension like this and not need to patch RT.