We have a ticket in our RT 3.6.6 installation containing correspondence which
belongs to a different ticket.
(A user followed up on a ticket using a new message with a changed subject
line, sent direct to one of my technicians, rather than replying to the RT
system's address.
The technician
Yeah, it can be that easy as described by Lars, however you loose
notifications when you move txns around using this way.
May be it's better to forward again to correct ticket and tender an
apology in another.
On Fri, Oct 31, 2008 at 5:23 PM, Lars Kellogg-Stedman [EMAIL PROTECTED] wrote:
I know
On Fri 31.Oct'08 at 13:40:01 -0400, Lars Kellogg-Stedman wrote:
Yeah, it can be that easy as described by Lars, however you loose
notifications when you move txns around using this way.
How hard would it be to add a move to another ticket option to each
transaction? Maybe one that's
Jesse == Jesse Vincent [EMAIL PROTECTED] writes:
How hard would it be to add a move to another ticket option to
each transaction? Maybe one that's only available on the
History page, rather than in the normal view? Or maybe just a
new permission to enable it? I know I've
Copy would be lovely. As would clone this transaction to a new ticket
So maybe in addition to Reply and Comment, and Forward on each
transaction, there would be a Clone? Should this be associated with
a new permission?
--
Lars Kellogg-Stedman [EMAIL PROTECTED]
On Fri, Oct 31, 2008 at 03:03:34PM -0400, Lars Kellogg-Stedman wrote:
Copy would be lovely. As would clone this transaction to a new ticket
So maybe in addition to Reply and Comment, and Forward on each
transaction, there would be a Clone? Should this be associated with
a new
I believe Dirk Pape has a Fork/Clone patch floating around out there. I
think it was him. I know I snagged it from somewhere.
Jesse Vincent wrote:
On Fri, Oct 31, 2008 at 02:56:33PM -0400, Lars Kellogg-Stedman wrote:
So, make it copy, and let the original copy be marked up as having
