Changes between Version 25 and Version 26 of TicketMoverPlugin


Ignore:
Timestamp:
Oct 3, 2016, 6:38:24 AM (5 years ago)
Author:
figaro
Comment:

Moved example to functional description

Legend:

Unmodified
Added
Removed
Modified
  • TicketMoverPlugin

    v25 v26  
    55== Description
    66
    7 This plugin allows you to move Trac tickets from one project to another, provided the projects reside 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.
     7This plugin allows you to move Trac tickets from one project to another, provided the projects reside in the '''same environment directory''', including attachments.
     8
     9If 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`:
     10
     11[[Image(screenshot.png, border=2)]]
     12
     13Install 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.
    814
    915There is a [https://github.com/UnwashedMeme/TicketMoverPlugin fork] of this plugin by UnwashedMeme that implements an `ITicketActionController` for moving tickets. Please open tickets for that version of the plugin in the [https://github.com/UnwashedMeme/TicketMoverPlugin/issues GitHub issue tracker].
    1016
    11 The similar DatamoverPlugin doesn't work for Trac 0.11 and is effectively deprecated. TicketMoverPlugin also handles ticket attachments.
     17[wiki: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)
    1218
    1319== Bugs/Feature Requests
     
    5561The environment variable `TRAC_ENV_PARENT_DIR` must be set in your web configuration or cgi/fcgi/wsgi script when running with a web server such as Apache with mod_wsgi/mod_python.
    5662
    57 == Project on Remote Server
    58 
    59 [wiki: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)
    60 
    61 == Example
    62 
    63 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`:
    64 
    65 [[Image(screenshot.png)]]
    66 
    6763== Recent Changes
    6864