Move Trac tickets from one project to another
Move Trac tickets from one project to another in the same environment directory. Install and enable the plugin and in the ticket sidebar controls will be shown to anyone with TICKET_ADMIN permission (by default) to move the ticket to another peer project where the user also has TICKET_ADMIN permissions.
If you have any issues, create a new ticket.
Download the zipped source from here.
Enable the plugin:
[components] ticketmoverplugin.ticketmover.ticketmover = enabled ticketmoverplugin.web_ui.ticketmoverhandler = enabled ticketmoverplugin.web_ui.ticketmoversidebar = enabled
Also make sure that the TicketSidebarProviderPlugin is enabled in the [components] section of your trac.ini:
ticketsidebarprovider.ticketsidebar.ticketsidebarprovider = enabled
Project on Remote Server
lkraav: I had a use case where I needed to move tickets between Tracs on two different machines. TicketMoverPlugin does not support this natively. To solve this, I mounted remote Trac project directory into a directory residing next to the local project directory over CIFS (certainly NFS or other network FS should work). This makes remote Trac appear local to TicketMoverPlugin and tickets were moved without errors. (10/06/09)
If you have permissions, a box will show up allowing you to move the current ticket to a different project. If you check the delete checkbox, the ticket will also be deleted from the database, though this is not recommended in most cases. If you don't delete the ticket, it will be closed with a resolution of moved.
Fixes #7496: Perform an explict cast of ticket_id to a string to avoid a programming error on PostgreSQL, where strict type checking is done. Prevent possibility of SQL injection since ticket_id comes from the request.
PEP8 formatting changes. Cleanup file and remove references to ClearSilver templates in documentation.
Originally developed at The Open Planning Project