id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,branch,changelog,apichanges,internalchanges 4686,Ticket duplication using Trac,olivermn@…,Christian Boos,"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.[[BR]] 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.[[BR]] 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.",enhancement,closed,normal,0.11,ticket system,,normal,fixed,copy ticketclone,,,,,