Clone Ticket

Doesn't work on closed tickets, was hoping to be able to use it to help resolve a data issue on a ticket that just closed.

The app would be good, if it would work. Unfortunately the app does not always produce a clone when firing. In a high percentage of situations there is no reaction. Sometimes it works, sometimes not. I spent a lot of time to identify a scenario when it does not work, but I couldn't. It seems that it has something to do with background jobs running when opening a ticket because sometimes it works after some waiting time.

Cloning works well, although it looks like the ticket needs to be solved for the app to fire. The resulting ticket does not inherit any attachments from the original, which is an essential component. There aren't many options related to the resulting ticket, clone can't be incorporated into triggers. I have not experienced the issue related to tickets not showing up in queues or search results.

The cloning app ignores if the original ticket has an internal note and changes it to a public note in the cloned ticket.  This is a deal breaker for us.  An internal note that is not meant for the customer to see suddenly is sent to the customer when the ticket is cloned.  Can you fix this?  Otherwise, this app is better referred to as the Clone-ish Ticket application.

We use your app to create ticket clones. However, is it possible to clone a ticket with a creation date similar to the cloned ticket? This is a great feature that this app misses to be perfect.