Ticket duplication using Trac

[olivermn@…]

It should be possible to create a new ticket by duplicating an existing ticket.

Use Cases

(from ​#th1214)

We just migrated to Trac from Bugzilla. The only feature we miss is the ability to clone a ticket into the new ticket fields. It would be great to have the Clone a Trac Ticket functionality.

(original request)

I'm hoping this has been done before and I'm just unable to find it. I have a collection of HW which assigns tasks to multiple teams when it arrives. To help manage this data I want to use Trac tasks. I have a GUI front end which solicits for all the data required in creating a task. It also solicits which teams are impacted. I want to create as many issues as there are teams impacted with the components of each driving the owner.

I then want to be able to use the front end to manage status on each of the opened tasks. So tickets 45, 46, 47 might all have the same data but have different components where Teams A, B, and C all have very different assignments.

I don't wish to reinvent the wheel. Is something similar to this already done?

tracking the status of an issue in different release lines

When there's a regression for a bug, instead of reopening the ticket (which will loose the information that this bug has been effectively fixed for the milestone indicated), one could duplicate it and schedule it for a given milestone on the other release line, see #4298.

creating ticket templates

One could have a wiki page with links to a few "typical" tickets that could be used as a templates for creating new tickets. Such tickets could have among other things prefilled descriptions, see #4044.

[anonymous]

As the author I wish to cancel.

[Christian Boos]

(this proposal sounded a bit like the "clone ticket" functionality … not sure there's already a ticket opened for that though)

[anonymous]

This is essentially cloning an existing ticket. Not an easy way to do this from my perspective. Have been trying to either use the macros to facilitate or to use eggs. Neither has been fruitful to date. What is the timeline for having clone feature. I found a clone defect that was a year old.

[Christian Boos]

What is the timeline for having clone feature. I found a clone defect that was a year old.

I was looking for a duplicate of this request but didn't find it… care to give the ticket number?

I agree that a Clone Ticket functionality can be useful in some scenarios, like one way to deal with the single issue, multiple releases problem (see #4298), or creating ticket templates (see #4044).

[olivermn@…]

I have written by own version and I'll post those changes here shortly. Up to you if you'd like to use this to close the other clone issue.

[ThurnerRupert <rupert.thurner@…>]

closed the other one as inferior proposal.

[schandler@…]

Replying to ThurnerRupert <rupert.thurner@gmail.com>:

closed the other one as inferior proposal.

FYI: There is still another clone request ​th:#1214 out there that is different enough, imho, from this ticket.

[Christian Boos]

​#Th1214 you meant ;-)

Well, I agree that the original description was not explicitly targeted at ticket duplication, it's only because of comment:2 and comment:3 that this ticket has been focused on the ticket cloning topic. I'll cleanup the description to reflect that, as otherwise I think that ​#Th1214 should be implemented in the base ticket system, for the reasons mentioned in comment:4.