Changes between Version 17 and Version 18 of TicketMoverPlugin


Ignore:
Timestamp:
Apr 25, 2015, 10:19:18 PM (9 years ago)
Author:
figaro
Comment:

Cosmetic changes

Legend:

Unmodified
Added
Removed
Modified

  • TicketMoverPlugin

    v17 v18  
    11[[PageOutline(2-5,Content,pullout)]]
    2 = Move Trac tickets from one project to another =
    32
    4 == Description ==
     3= Move Trac tickets from one project to another
    54
    6 Move Trac tickets from one project to another that resides 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.
     5== Description
     6
     7Move Trac tickets from one project to another that 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.
    78
    89I probably would have used the DatamoverPlugin (now deprecated), but this didn't work for Trac 0.11. TicketMoverPlugin also handles ticket attachments.
    … …  
    1011There 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].
    1112
    12 == Bugs/Feature Requests ==
     13== Bugs/Feature Requests
    1314
    1415Existing bugs and feature requests for TicketMoverPlugin are
    … …  
    1819[http://trac-hacks.org/newticket?component=TicketMoverPlugin&owner=k0s new ticket].
    1920
    20 == Requirements ==
     21[[TicketQuery(component=TicketMoverPlugin&group=type,format=progress)]]
     22
     23== Requirements
    2124
    2225This plugin requires TicketSidebarProviderPlugin and TracSqlHelperScript.
    2326
    24 == Installation ==
     27== Installation
    2528
    2629Download the zipped source from [download:ticketmoverplugin here].
    … …  
    2831You can also check out TicketMoverPlugin from [http://trac-hacks.org/svn/ticketmoverplugin here] using Subversion, or [source:ticketmoverplugin browse the source] with Trac.
    2932
    30 Enable the plugin:
     33Enable the plugin in your `trac.ini` file:
    3134
    32 {{{
    33 #!ini
     35{{{#!ini
    3436[components]
    3537ticketmoverplugin.ticketmover.ticketmover = enabled
    … …  
    3840}}}
    3941
    40 Also make sure that the TicketSidebarProviderPlugin is enabled in the `[components]` section of your `trac.ini`:
     42Also make sure that the TicketSidebarProviderPlugin is enabled in the `[components]` section of your `trac.ini` file:
    4143
    42 {{{
    43 #!ini
     44{{{#!ini
     45[components]
    4446ticketsidebarprovider.ticketsidebar.ticketsidebarprovider = enabled
    4547}}}
    4648
    47 The permission required for moving ticket can be specified (default value is shown):
     49The permission required for moving a ticket can be specified (default value is shown):
    4850{{{
    4951#!ini
    … …  
    5254}}}
    5355
    54 == Project on Remote Server ==
     56== Project on Remote Server
    5557
    5658[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)
    5759
    58 == Example ==
     60== Example
    5961
    60 See screenshot:
     62If 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`:
    6163
    6264[[Image(screenshot.png)]]
    6365
    64 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`.
    65 
    66 == Recent Changes ==
     66== Recent Changes
    6767
    6868[[ChangeLog(ticketmoverplugin, 3)]]
    6969
    70 == Author/Contributors ==
     70== Author/Contributors
    7171
    7272''Originally developed at [http://openplans.org The Open Planning Project]''